SBCE 8.1.1 Offer Definition

__________________________________________________________________________________________________
Offer Definition
Avaya Session Border Controller

for Enterprise Release 8.1.1
DOCID 190249
Content of this offer definition applies to Avaya ASBCE® 8.0, 8.0.1, 8.1 and 8.1.1 and will continue to be updated over time as
needed unless otherwise noted. Please ensure you have downloaded the latest version (see Change Control.)
© 2020 Template Rev 1.0 Avaya Inc. All Rights Reserved.

Avaya and the Avaya Logo are trademarks of Avaya Inc. and are registered in the United States and other countries.
All trademarks identified by ®, TM or SM are registered marks, trademarks, and service marks, respectively, of Avaya Inc.
All other trademarks are the property of their respective owners. Avaya may also have trademark rights in other terms used herein.
References to Avaya include the Nortel Enterprise business, which was acquired as of December 18, 2009.
02/10
Avaya Inc. – Proprietary. 1

Use pursuant to the terms of your signed agreement or Avaya policy.
Version Control
Product ➔ Avaya ASBCE® 8.0, 8.0.1, 8.1 GA Date ➔ 08/04/2020

and 8.1.1
Rev # Rev Date
1.0 08/03/2020
Avaya Source Prime Channel Partner Target Audience

Jerome Joanny Product Management, Order Management, Documentation,
Training, Lab Engineers, Sales Engineers
CHANGE CONTROL RECORD
Date Issue/Version # Prime Summary of Changes
(mm/dd/yy)
08/03/2020 1.0 Jerome Joanny First published Version

Table of Contents
1 About this document ................................................................................................................................................... 6
1.1 Non-Disclosure....................................................................................................................................................................................................................................................... 6
1.2 Globalization ........................................................................................................................................................................................................................................................... 6
2 Avaya Session Border Controller for Enterprise solution ...................................................................................... 7

3 About ASBCE 8.1.1 ...................................................................................................................................................... 9
3.1 Why upgrade to ASBCE 8.1.1............................................................................................................................................................................................................................... 9
3.1.1 Extended Manufacturer Software Support Release ......................................................................................... 10
3.2 ASBCE solution components ............................................................................................................................................................................................................................. 11
3.3 ASBCE deployment options ............................................................................................................................................................................................................................... 12
3.3.1 Virtualized environment .................................................................................................................................. 12
3.3.2 Avaya Virtualization Platform (AVP) [8.0.1] .................................................................................................... 12
3.3.3 Server Appliance (not virtualized aka Bare metal) .......................................................................................... 13
3.3.4 Discontinued Hardware appliance with Release 8.......................................................................................... 16
3.3.5 Cloud Deployments ......................................................................................................................................... 17
3.3.6 Discontinued Virtualization platform support with Release 8 ........................................................................ 17
4 ASBCE 8.1.1 ............................................................................................................................................................... 18
4.1 Overview................................................................................................................................................................................................................................................................ 18
4.2 Business Partner Value Proposition ................................................................................................................................................................................................................... 18
4.2.1 Market Needs, trends and Growth .................................................................................................................. 18
4.2.2 Value Proposition............................................................................................................................................. 19
4.2.3 Defensible Differentiators............................................................................................................................... 20
4.2.4 Partner Business and Strategic Value .............................................................................................................. 21
4.2.5 Avaya Support for Go-to-Market..................................................................................................................... 23
5 ASBCE 8.0, 8.0.1, 8.1 and 8.1.1 Feature descriptions ............................................................................................ 24
5.1 Simplification of the ASBCE user experience ................................................................................................................................................................................................... 24
5.1.1 Simplified and Improved Backup & Restore [8.0] ......................................................................................... 25
5.1.2 More robust and seamless upgrade [8.0] ........................................................................................................ 25
5.1.3 CLI introduction for Improved pre-staging /system prepping [8.0] ............................................................. 25
5.1.4 Simplified Certificate Management [8.0]........................................................................................................ 25
5.1.5 Non-intrusive Multi tenancy setup thru on the fly configurations changes [8.0] .......................................... 26
5.1.6 Reverse Proxy using TLS Server Name Indication (TLS SNI) [8.0.1] ........................................................... 26
5.1.7 Removal of Volume Tiered pricing for a simpler ordering experience [8.0] .................................................. 26
5.1.8 SNMP alarming when ASBCE is nearing session saturation [8.0] ................................................................ 27
5.1.9 Deployment Automation & Configuration API [8.1] ..................................................................................... 27
5.1.10 Manageability via Equinox iView [8.1]........................................................................................................... 27
5.1.11 SIP, TURN, PPM and HTTP logs in EMS [8.1] ........................................................................................... 27
5.1.12 Support for FQDN/DSN SRV registration [8.1] ............................................................................................ 28
5.1.13 Dynamic Licensing for Mid-market [8.1] ....................................................................................................... 28
5.1.14 Support for Security only patches [8.1] ........................................................................................................... 28
5.2 Better Together with Equinox ............................................................................................................................................................................................................................ 28
5.2.1 MSFT Edge Browser support for WebRTC communications [8.0] ............................................................... 28
5.2.2 Greater Turn capacity for WebRTC client aka Increased Media Tunneling capacity [8.0] .......................... 28
5.2.3 Http Tunneling through Proxy SSL inspection mode [8.0] ........................................................................... 29
5.3 Better integration for SIP contact center with Aura ......................................................................................................................................................................................... 29
5.3.1 Support for Extended host name validation [8.0] ........................................................................................... 29
5.3.2 Support for Call preservation [8.0] .................................................................................................................. 29
5.3.3 Multi-destination SIPREC [8.1]...................................................................................................................... 30
5.4 Opening Up the SBCE architecture to ecosystem ............................................................................................................................................................................................ 31
5.4.1 Allowing ASBCE core routing decision engine connection to external data set (LDAP) [8.0] ..................... 32
5.4.2 Linking SBCE Help to Avaya learning Administrator training [8.0] ............................................................. 32
5.4.3 Microsoft Skype For Business certification for 8.x release train [8.0.1].......................................................... 32
5.4.4 Microsoft Teams certification for Direct Routing with no Media Bypass [8.1.1]........................................... 33
5.5 Overall UC solution TCO improvements [8.0.1].............................................................................................................................................................................................. 33
5.5.1 Support for Shared AAMS instance [8.0.1]...................................................................................................... 33
5.5.2 Preloading of trust for Avaya Device Enrollment Services [8.0.1] .................................................................. 33

5.6 Technology currency & Security ......................................................................................................................................................................................................................... 34
5.6.1 Avaya Security Common Engineering Criteria compliance [8.0]................................................................... 34
5.6.2 Remote Workers MAC based authentication [8.0] ......................................................................................... 34
5.6.3 Logging CEC compliance [8.0.1] ................................................................................................................... 34
5.6.4 JITC compliance [8.1] ..................................................................................................................................... 35
5.6.5 GDPR/CCPA compliance [8.1] ...................................................................................................................... 35
5.6.6 Two Factor Authentication for Privileged Users [8.1] .................................................................................... 35
5.6.7 Single Sign on for Privileged Users [8.1] ........................................................................................................ 36
5.7 Next Generation 911............................................................................................................................................................................................................................................ 36
5.7.1 URN invite [8.1] .............................................................................................................................................. 36
5.7.2 URN Mapping [8.1] ........................................................................................................................................ 36
5.8 Platform support................................................................................................................................................................................................................................................... 37
5.8.1 Support for vSphere 6.7 [8.0] ........................................................................................................................... 37
5.8.2 ASP Hardware appliances [8.0] ...................................................................................................................... 37
5.8.3 Improved cost effectiveness for SMB with new low-end appliance (CAF251) introduction [8.0.1] ............... 37
5.8.4 Support for Avaya Virtualization Platform [8.0.1] ........................................................................................... 37
5.8.5 Support for Dell R340 – new mid-size appliance [8.1] .................................................................................... 38
5.8.6 Support for SBCE HA in Amazon Web Services (AWS) [8.1.1] ...................................................................... 38
5.8.7 Simplex deployment in Microsoft Azure [8.1.1] ............................................................................................... 38
6 Upgrading to ASBCE 8.1.1 ........................................................................................................................................ 39
6.1 Upgrade IPOSS customers from ASBCE 7.x to 8.1.1 ..................................................................................................................................................................................... 39
6.2 Supported upgrade paths to ASBCE 8.1.1 ........................................................................................................................................................................................................ 40
6.3 Upgrading the Hardware appliance .................................................................................................................................................................................................................... 40
6.3.1 Upgrading from Hardware no longer supported in R8.1.1 ............................................................................. 40
6.3.2 Upgrading from CSR2 or CSR3 to ACP........................................................................................................... 41
6.4 Upgrade material codes and Pricing ................................................................................................................................................................................................................... 41
6.4.1 ASBCE for Aura / Enterprise .......................................................................................................................... 41
6.4.2 ASBCE for MM/IPO ...................................................................................................................................... 42
7 Product Specifications .............................................................................................................................................. 44
7.1 Compatibility with Avaya Solutions ................................................................................................................................................................................................................... 44
7.1.1 Avaya Call Servers ........................................................................................................................................... 44
7.1.2 Avaya Endpoints ............................................................................................................................................. 45
7.2 Interoperability with 3rd Parties ........................................................................................................................................................................................................................... 46
7.2.1 3rd parties Call Server ...................................................................................................................................... 47
7.2.1 Internet Telephony Server Providers .............................................................................................................. 47
7.2.2 SIPconnect ...................................................................................................................................................... 48
7.2.3 3rd parties SIP endpoints ................................................................................................................................. 48
7.3 Solution capacities and Performance.................................................................................................................................................................................................................. 49
7.3.1 Solution capacities quick reference ................................................................................................................ 49
7.4 Virtualization Resource Profiles.......................................................................................................................................................................................................................... 52
7.4.1 Summary Table for Resource Profile and capacity ........................................................................................ 53
7.5 Supported Hypervisors for Virtualized environment ....................................................................................................................................................................................... 53
7.5.1 VMWare vSphere ............................................................................................................................................ 54
7.5.2 KVM ................................................................................................................................................................ 54
7.5.3 Nutanix AHV .................................................................................................................................................. 54
7.5.4 AWS ................................................................................................................................................................. 54
7.5.5 Azure ............................................................................................................................................................... 55
7.6 Supported Browsers ............................................................................................................................................................................................................................................. 55
7.7 Supported Hardware ............................................................................................................................................................................................................................................ 55
7.7.1 Physical appliance .......................................................................................................................................... 55
7.7.2 Hardware support for Virtual Appliance ........................................................................................................ 55
8 Product documentation ............................................................................................................................................ 56
8.1 Release Notes ........................................................................................................................................................................................................................................................ 56
8.2 User and System documentation ........................................................................................................................................................................................................................ 56
9 Avaya Learning .......................................................................................................................................................... 58

9.1 Avaya Learning Center ......................................................................................................................................................................................................................................... 58
10 Product Ordering, Licensing and Pricing ............................................................................................................... 67

10.1 Quoting and Ordering Tools/Procedures ......................................................................................................................................................................................................... 67

10.1.1 ASBCE in A1S ................................................................................................................................................. 68
10.1.2 ASBCE 8.1.1 with IP Office 11.x (or above) .................................................................................................... 69
10.2 Buy to Current ...................................................................................................................................................................................................................................................... 69
10.3 Suite Licensing with Avaya Aura ........................................................................................................................................................................................................................ 70
10.4 Product Order Codes, structure and Pricing ..................................................................................................................................................................................................... 70
10.4.1 License Structure ............................................................................................................................................ 70
10.4.2 Product Codes and Pricing ............................................................................................................................. 77
10.4.3 Virtual Appliance Order codes and Pricing .................................................................................................... 83
10.4.4 Azure order Codes and Pricing ....................................................................................................................... 84
10.4.5 Hardware Appliances Order codes and Pricing ............................................................................................. 85
10.4.6 Product Bundling............................................................................................................................................ 86
11 System Engineering Consideration ......................................................................................................................... 86
11.1 Prerequisites .......................................................................................................................................................................................................................................................... 86
11.2 Network Rules ...................................................................................................................................................................................................................................................... 87
11.3 Network Design & Best practices....................................................................................................................................................................................................................... 89
11.4 Configuration Tool and Misc. Engineering Tips .............................................................................................................................................................................................. 90
11.4.1 Configuration Tool ......................................................................................................................................... 90
11.4.2 Misc. Engineering Tips .................................................................................................................................. 90
11.4.3 Specific Engineering Rules for Mid-Market deployments .............................................................................. 91
12 Product Licensing Process and Policies ................................................................................................................ 91
12.1 PLDS licenses........................................................................................................................................................................................................................................................ 91
12.2 Temporary license Requests ................................................................................................................................................................................................................................ 94
12.3 Lab Trials ............................................................................................................................................................................................................................................................... 94
13 Services and Support ................................................................................................................................................ 95

13.1 Pre- Sales Support................................................................................................................................................................................................................................................. 95
13.2 Services Support Offers ....................................................................................................................................................................................................................................... 95
13.2.1 APS and Installation Support.......................................................................................................................... 95
13.2.2 Customer Care/Support ................................................................................................................................. 96
13.2.3 Maintenance Services ..................................................................................................................................... 97
13.3 Remote Access and Maintenance ....................................................................................................................................................................................................................... 98
13.3.1 SAL Remote Access for Enterprise/Aura Customers .................................................................................... 99
13.3.2 SSL VPN Access for IP Office customers ...................................................................................................... 99
13.3.3 iLO and iDRAC with ASBCE hardware appliances ....................................................................................... 99
13.4 PCN/PSN Strategy ............................................................................................................................................................................................................................................ 100
13.4.1 Product Correction Notice (PCN) ................................................................................................................. 100
13.4.2 Product Support Notice (PSN) ...................................................................................................................... 100
13.5 Technical Consulting System Support.............................................................................................................................................................................................................. 100
13.6 Enhanced Services Available ............................................................................................................................................................................................................................. 100
13.6.1 Avaya Operations Services – UC Managed Assist and UC Managed Operate ............................................. 100
13.6.2 Remote Configuration Helpline (RCH) ........................................................................................................ 101
13.6.3 Remote Access via Secure Access Link Gateway .......................................................................................... 101
13.6.4 Remote Diagnostics via Avaya Diagnostic Server ......................................................................................... 102
13.7 Warranty .............................................................................................................................................................................................................................................................. 102
13.7.1 Post Warranty support ................................................................................................................................... 102
13.8 Repair & Return, Logistics ................................................................................................................................................................................................................................. 102
13.8.1 Dead on Arrival (DOA)/Out of Box Failure (OBF) ...................................................................................... 103
14 Avaya DevConnect .................................................................................................................................................. 103
15 Contact Information ................................................................................................................................................ 103

1 About this document
This document provides detailed information on the Avaya Session Border Controller for Enterprise release
8.0, 8.0.1, 8.1 and 8.1.1 (ASBCE 8.x) commercial offer that services both Aura and IP Office.
This document is targeted for Channel Partners, Distributor-Product Managers, Sales, Engineering, Order
Management, Servicing, Documentation and Training personnel and serves as a comprehensive guide for
partner and distributor readiness.
Avaya continues to evolve, expand and enhance continuously its Session Border Controller for Enterprise.
The delivery of release 8.x of Avaya ASBCE builds on previous releases and adds new content supporting
small to very large enterprise systems, complex xCaaS offers and the large Contact Center environment.
The Commercial Offer of Avaya Session Border Controller for Enterprise (ASBCE) release 8.0 went GA on
February 11th, 2019.
The Commercial Offer of Avaya Session Border Controller for Enterprise (ASBCE) release 8.0.1 went GA
on August 13th, 2019.
The Commercial Offer of Avaya Session Border Controller for Enterprise (ASBCE) release 8.1 went GA on
January 24th, 2020.
The Commercial Offer of Avaya Session Border Controller for Enterprise (ASBCE) release 8.1.1 went GA
on August 4th, 2020 and is now the only SBCE 8.x release active, supplanting any of its 8.x predecessor
from a technical support point of view.
This document is intended as a ‘living’ document. Updates will be periodically posted to the Sales Portal.
 Please ensure you have downloaded the latest version (see Change Control).
1.1 Non-Disclosure
The Avaya non-disclosure processes will be followed for any documentation and information being released
to the End Customer or any type of Channel Partner’s personnel not covered by a contract with Avaya prior
to GA
1.2 Globalization
This document is written as a global document. Unless specifically noted, all information applies across all
theatres. Theatre specific information will be identified using the regional designations listed below.
• United States (US)
• Caribbean and Latin America and Canada: (AI)
• Europe, Middle East and Africa (EMEA)
• Asia Pacific (APAC)

2 Avaya Session Border Controller for Enterprise solution
ASBCE release 8.1.1 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.1 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.1.1 will replace the existing Avaya Session Border
Controller for Enterprise (ASBCE) release 7.2.2, 8.0, 8.0.1 and 8.1 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.1.1. By selecting
deployment with R7, one will be granted access to both R8 and R7 downloads in PLDS.
ASBCE release 7.1.0 will be retire from new sales Summer 2020 as Release 8.1 has reached the Joint
Interoperability Testing Command (JITC) certification and is now posted on the DISA Approved Product List
(APL). The current ASBCE Service Pack meeting JITC certification requirements is Release 8.1 at the time
of issuance of this document. (check Avaya support site for update on the latest Service Pack available).
The feature and other elements describe in this offer definition solely applies to Release 8.0, Release 8.0.1,
Release 8.1 and Release 8.1.1.
ASBCE brings key values to the Avaya SIP Unified Communication solution set:
• ASBCE focuses on the Enterprise, Mid-Market 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.1.1 significantly improve ASBCE partners and customers overall
experience, with Direct Routing Certification for Microsoft Teams, SBCE HA support in AWS and Simplex
deployment in Azure
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 (ASBCE) at the edge of
the Enterprise network since all SIP ingress/egress traffic crosses the ASBCE.
The diagram below shows the ASBCE in its space as the UC security ‘edge’ in a customer network
ASBCE resides at the edge of the network and securely enables secure 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.
A more detailed view of ASBCE supported applications is covered in this section of this document.
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.
3 About ASBCE 8.1.1

Avaya Session Border Controller for Enterprise 8.1.1 is the latest release of the ASBCE software and is the
first feature pack of the SBCE 8.1 release, which is SBCE EMSPP release. It is inclusive of all functionalities
previously introduced in the 7.x and previous 8.x release trains and is the latest and greatest generation of
Avaya’s session border controller for team and customer engagement solutions.
3.1 Why upgrade to ASBCE 8.1.1

Avaya Session Border Controller for Enterprise 8.1.1 is the latest release for the Avaya Session Border
Controller product line and simply its best release yet. Building on top of Release 8.1, This feature pack release
provides new capabilities to enable improved cloud support. The second major focus of release 8.1.1 is Direct
Routing certification with Microsoft Teams.
On top of the several major features initially introduced with Release 8.0, Release 8.1.1 also delivers key
values as improved cloud support and Microsoft interoperability.
The key features delivered so far in Release 8.x are:

- Improved cost effectiveness for SMB with new low-end appliance (CAF251) introduction [8.0.1]
- Microsoft Skype For Business certification for 8.x release train [8.1]
- Overall UC solution TCO improvements with support for Aura AVP, preloaded DES trust and ability to share
common AAMS [8.0.1]
- Multi Destination SIPREC [8.1]
- Dynamic Licensing availability for Mid-Market [8.1]
- URN invite support for NG911 [8.1]
- URN mapping – Basic call for NG911 [8.1]
- Support for Frequent security patches [8.1]
- SBCE HA support in AWS [8.1.1]
- Azure deployment (simplex only) [8.1.1]
On the simplicity of the UX front the following features are now available since ASBCE 8.1:
• Simplified deployment (backup/restore, upgrade, and configuration)
• Simplified Certificate Management
• Non-intrusive Multi tenancy setup thru on the fly configurations changes
• Multi-tenancy improvement with TLS SNI for reverse Proxy [8.0.1]
• Removal of Volume Tiered pricing for a simpler ordering experience
• Bundling of ASBCE software and Hardware for small to very small business as part of an ASBCE 8.0
Launch promotion
• SNMP alarming when ASBCE is nearing session saturation
• New and updated SBCE Configurator -A1S [8.0.1] (started in 8.0.1 and will continue thru 2019)
• Pre-loading of trust with DES [8.0.1]
• Deployment Automation & configuration API [8.1] as a prelude to yet to come templated configurations
feature and 3rd party management platforms configuring the SBCE.
• SIP, Turn, PPM & HTTP logs now available in the logs Section of EMS [8.1]
• Support for FQDN/DSN SRV for ITSP registration [8.1]
To deliver an improve solution experience with Equinox
• MSFT Edge Browser support for WebRTC communications
• Http Tunneling through Proxy SSL inspection mode
• Increased media tunneling capacity
For Better reliability for SIP contact center with Aura
• Support for Extended host name validation
• Support for Call preservation
Opening the core ASBCE solution to external ecosystems:
• Allowing ASBCE core routing decision engine connection to external data set (LDAP)

• Linking ASBCE Help to Avaya learning Administrator training
• Microsoft Skype For Business certification [8.0.1]
• Microsoft Teams Direct Routing certification with no media Bypass [8.1.1]
For overall Avaya UC solution TCO improvement [8.0.1]:
• Support for AVP as additional platform [8.0.1]
• Ability to leverage shared AAMS instance [8.0.1]
• Pre-loading of trust with DES [8.0.1]
On the cost effectiveness front:
• Introduction of the CAF251 for Aura and IPO – additional low-end hardware appliance support [8.0.1]
And finally, the Technology currency elements:

• Support for latest Avaya Hardware Converged Platform (ACP) for the two highest capacities
appliances
• Support for vSphere 6.7
• Remote Workers MAC based authentication
• Continuous improvement to ensure adherence to Avaya security best practices (Trust and cert
management, Dos Firewall and Malware protection, OS hardening)
• Support for R340 mid-size appliance [8.1]
3.1.1 Extended Manufacturer Software Support Release

Avaya Session Border Controller for Enterprise 7.1.0 is designated and remains as the Extended Manufacturer
Software Support release for the 7.x JITC release stream.
As Release 8.1 EMSSP has now reached the DISA APL, Release 7.1.0.x should be expected to go into
imminently into End of Life cycle.(check End of Sales announcement for any further details).
Avaya’s Extended Manufacturer Software Support Policy (EMSSP): offers an additional category of support
for certain releases of products allowing those products to be sold and supported for an extended and
predictable period.
Once a release has been designated as EMSS, Avaya will

• Continue to sell the EMSS release for a minimum period of two (2) years and
• Support the release for a minimum of three (3) years from its date of first sale.
(Support meaning design service packs, bug fix, security updates)

3.2 ASBCE solution components
Avaya Session Border Controller for Enterprise 8.1.1 continues as a single software product that can serve
many applications needs for SIP-based communications in the Enterprise.
The software, on all physical or virtual platforms, is ‘self-contained’ as an appliance and is delivered, with our
Business Partners in mind, pre-loaded on the hardware platforms, on DVD or on a Thumb Drive for physical
media (platform dependent), and, aligning with other Avaya applications, via PLDS.
The solution is composed of four main components:

• The ASBCE software itself: this is the component in the path of each SIP, Turn or http Tunneled call
crossing the edge of the network.
• The EMS software: the only software component included in the EMS is a user Interface application
whose role is to offer a graphical user interface into the management of the ASBCE instances. This
component is required when you want to efficiently manage at least one HA pair. The Portwell model,
or a standalone non-HA ASBCE, can be managed thru its own embedded EMS software instance
• The Operating System: ASBCE 8.1.1 uses a customized version of Red Hat Enterprise Linux (RHEL
7.7) as its server operating system. The customization of the OS is performed to optimize the system
performance and maximize the system security (removal of unused libraries to reduce surface of
attack etc.)
• The Hardware appliance: This is an optional element (see this section for platform options) and only
required when the customer selects to deploy the ASBCE as a physical appliance component of its
network.
The ASBCE and EMS software can be jointly deployed in several redundancy configurations from the lowest
stand alone, to a full HA geo redundant pair, offering great flexibility in the selection of reliability levels vs cost
/complexity.
The following graphic represents the different redundancy options available for the ASBCE and the associated
tradeoffs of cost & complexity.

The EMS standalone software is only required when a customer is considering deployment of a system
constituted of multiple ASBCEs which it would like to manage centrally or any ASBCE deployed in HA mode.
A stand alone, non- HA ASBCE could be deployed jointly with the EMS software requiring only a single OVA
deployment.
The EMS software can also be deployed in a highly redundant configuration as Active-Active, only requiring
layer 3 network connectivity (i.e. no requirement for L2 networking) between the two locations (typically two
Geo Redundant Areas ) where the EMS are located.
3.3 ASBCE deployment options
The following sub sections are describing the different platform options available for the ASBCE in its R8.x
release train
3.3.1 Virtualized environment

ASBCE 8.1.1 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.
Note: Capacities provided by the ASBCE Virtual Machine OVA, also known as Virtual Appliance or
Vapp, and as validated on VMware ESXi 6.7, are limited compared to a bare-metal appliance
implementation due to hypervisor processing capabilities. Refer to the section of this document,
Product Specifications, for more details.
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
Deployment configurations, i.e. SA vs HA models are similar as with physical appliance, with extra due
diligence required for IP addressing and placement on the physical hosts supporting the VMware
environment.
As such virtualization is a ‘platform’ choice and implementation of ASBCE as Vapp or physical appliance is
up to ASBCE’s customer preference. There is no right or wrong choice – to the exception of capacity, both
Vapp and physical appliances provides the same level of reliability, feature and security.
3.3.2 Avaya Virtualization Platform (AVP) [8.0.1]

New since Release 8.1, SBCE now supports deployment onto Avaya Virtualization platform (aka AVP) as of

Aura 8.1 (i.e. AVP 8.1 and SDM client 8.1 are required at a minimum).
For full SDM client and SDM embedded in SMGR support with SBCE, Aura 8.1.2 is required. (deployment
only, upgrade management is not supported at this stage).
The deployment of SBCE 8.1 is also limited to the ACP120 (now ASP120) or CSR2 or CSR3 hardware
models. Deployment on top of AVP in an 8300e blade is not supported at this stage.
The EMS function supports deployment in shared AVP mode (EMS can share the AVP appliance with other
Avaya application)
In this initial release, the SBCE function only supports deployment in dedicated AVP mode (SBCE is the only
application on top of one AVP appliance)
The sizing and performances of SBCE on AVP have been included in the August 2019 release of A1S and
are identical to the performances of the SBCE in a VE (customer provided VMware) environment.
3.3.3 Server Appliance (not virtualized aka Bare metal)

New ASP hardware support (P3 and P5 models) has been introduced in ASBCE 8.x replacing the formerly
called CSR3 Hi-Cap and CSR3 Hi-Cap with Accelerator appliance.
Note: G9, G8 based appliances will continue to be supported throughout the Release 8 cycle.
However, since Avaya Software and Avaya Hardware follow independent lifecycle paths, customers
should pay attention to any relevant Hardware End of Life announcement to confirm the lifecycle
status of the appliance, they are planning to run their ASBCE R8 software on.
No additional networking components are needed for the ASBCE itself. The servers are shipped complete
with rack mounting rail kits (Dells and HPs) or mounting tabs, and a cable kit for initialization activities and
monitoring. The servers also come with a US power cord in the box. It is assumed that the customer has or
is ordering the appropriate Call Server gear, country-appropriate power cords if necessary, and the edge
router/firewall for the implementation and the necessary LAN equipment are available.
Note: ASP P5 based appliance offer 4x1Gb NICs and 2X10Gb NICs – the 10Gb NICs do not come with the
SFP transceivers out of the box and Customers need to order these separately either via Avaya (part
available on Avaya OneSource) or provide their own. Both GigE or fiber interface are supported with release
8.x
New starting with Release 8.1, support for a new mid-size appliance, Dell R340, has been introduced.
Additionally, and since Release 8.0.1, a new low-end appliance has been added to the SBCE hardware
appliance portfolio: Portwell CAF251.
The CAF251 is available in all region where the CAD230 is sold and is available for both Enterprise and Mid-
Market segment (different SKU but identical hardware).
The Portwell CAF251 pricing is roughly half of the one of the CAD230 and its capacity is limited to 100 session
max, for SIP trunking and Avaya remote workers, non-upgradeable, i.e. if a customer is expected to grow
beyond the 100 Sessions capacity then a CAD230 or larger appliance should be preferred.
To help with planning your appliance upgrade, the following table provide a convenient historical perspective
of the server appliance hardware supported (or not) by each one of the 6.3, 7.x and 8.x releases:
Server
7.1.0.x 7.2.x 8.0 8.0.1 8.1 8.1.1
Hardware
CAD208 Yes Yes No No No No
CAD230 No Yes Yes Yes Yes Yes

CAF251 No Starting Yes Yes
No No
with 8.0.1
Dell R210-II Yes Yes No No No No
Dell R210-II No No No No
Yes Yes
(EMS)
Dell R320 Yes Yes Yes Yes Yes Yes
Dell R330 No Yes Yes Yes Yes Yes
Dell R340 Starting Yes
No No No No
with 8.1
HP DL360 G8 Yes Yes Yes Yes Yes Yes
HP DL360 G9 Yes Yes Yes Yes Yes Yes
ASP P3 Starting with Yes Yes Yes Yes
No
7.2.2.2
ASP P5 Starting with Starting with Yes Yes Yes Yes
7.1.0.8 7.2.2.2
3.3.3.1Aura/Enterprise Segment
Specifications for the hardware platforms that are supported by ASBCE 8.1.1 are detailed below. The
hardware platforms are:
• High Capacity HP DL360G9 w/ACC and Dell R630 w/ACC (this platform is supported for upgrade
until its End of Manufacturing support date and new sales until its End of Sales date) – The Hi-
capacity platforms can be augmented for higher capacities by addition of an accelerator card. This
card will be installed at the factory, and there are different ordering codes for the release 7.2 “w/ACC”
versions of the server. These platforms continue to come with dual power supplies and hot-swap
hard drives and leverages dual hex-core CPUs. They can be used for either EMS or core ASBCE
application or can also be deployed with both EMS and core co-resident. The substitute for this
hardware appliance once it goes End of Sale is going to be the Avaya Common Platform 110
(ACP110) Profile 3 and Profile 5. Please refer to Release 7.2.2 Version of the ASBCE offer definition
for detailed hardware specifications of the Hi cap w/ acc hardware.
• Avaya converged Platform 110 – Profile 3 – a High Range platform for Enterprise, replacing the Hi-
Cap servers – Support for this platform is newly introduced in Release 8.0 at GA. This platform has
dual Intel Skylake CPU 2.2Ghz for a total of 20 physical cores, 6x1Gb NICs, dual power supplies
750 watts and hot-swap HDD. It can be used for either EMS or core ASBCE application or can also
be deployed with both EMS and core co-resident. Please refer to table below for more details on
hardware specifications.
• Avaya Converged Platform 110 - Profile 5 - – The Highest Range platform for Enterprise in the
appliance, replacing the Hi-cap servers with Accelerator – Support for this platform is newly
introduced in Release 8.0 at GA. This platform has dual Intel Skylake CPU 2.6Ghz for a total of 28
physical cores, 4x1Gb NICs,2x10Gb NIC ( SFP+), dual power supplies 750watts and hot-swap
HDD. The 10Gb SFP needs to be purchased separately in A1S or source via 3rd party and can either
be GigE or Optical. It can be used for either EMS or core ASBCE application or can also be deployed
with both EMS and core co-resident. Please refer to table below for more details on hardware

specifications.
• HP DL360G9 Mid-range – A Mid-Range platform for Enterprise – this platform is supported for
upgrade only. This platform has single CPU, dual power supplies and hot-swap hard drives. It can
be used for either EMS or core ASBCE application or can also be deployed with both EMS and core
co-resident. Please refer to Release 7.2.2 Version of the ASBCE offer definition for detailed hardware
specifications.
• Dell R330 & R340 – this platform is supported for new sale and upgrade – it is a Mid-Range appliance
supported with Release 8.0 for new sale. This platform has single CPU, dual power supplies and
hot-swap hard drives. It can be used for either EMS or core ASBCE application or can also be
deployed with both EMS and core co-resident. New in Release 8.1, the R330 will be replaced
progressively by the R340 (hardware refresh) as the R330 stock depletes.
• Portwell CAD-0230 and CAF-0251 – supports the core as well as the co-resident Element
Management System in SA configurations for smaller Enterprise/Aura systems and the IP Office
systems
Specification Low Range ASBCE(Portwell) Mid-Range ASBCE High Range ASBCE

CAD230 CAF251 Dell High
Dell -ACP110 Profile 3 Range ASBCE
Dell – ACP110- Profile 5
Product Type ASBCE CORE/EMS ASBCE CORE/EMS ASBCE CORE/EMS ASBCE CORE/EMS ASBCE CORE/EMS
Part Number 388052/388053 700514948/700515001 388048/388049 700514264 700514265
Platform Type CAD-0230-4611 700515001
CAF-0251 PE R330 (CSR3 OEM) Dell R640XL 1U server Dell R640XL 1U server
BIOS R1.01 (Avaya only) Standard TBA TBA TBA
Intel Celeron N3350, 2C Xeon E3-1220 v5- 3.0 GHz Intel Skylake 2.2Ghz Intel Skylake 2.6Ghz
Processor ATOM C2358 – 1.7GHz (2M Cache, up to 2.4 GHz) (4 cores - 80W) S-4114 -10 cores G-6132 – 14 cores
Number of CPU sockets 1 1 1 2 2
2GB DDR3L 1333MHz DDR3L 4GB on board 8GB (2X 4GB) DDR4 48 GB ( 6x 8Gb ) DDR4 RDIMMs 192 GB ( 12x 16Gb) DDR4 RDIMMs
Memory SODIMM 2133MT/s ECC UDIMM
RAID No No RAID 1 RAID 6 RAID 6
Specification Low Range ASBCE Mid-Range ASBCE High Range ASBCE
Portwell Dell Dell -ACP110 Profile 3 Dell – ACP110- Profile 5
Hard Drives 500GB (SATA) 64GB 2 X 300GB 10K (SAS) 4x600Gb 10K – 2.5” 6x600Gb 10K – 2.5”
SATADOM,Innodisk
64GM41BC1SCA-H82
+ EMMC 4GB onboard
Optical Drive No No DVD+/-RW 9.5mm SATA DVD-ROM optical drive 9.5mm SATA DVD-ROM optical drive
Interfaces (Ports)
Data 6 X 1GbE 4x1GbE 6 X 1GbE 6 X 1GbE 4X 1GbE – 2 x 10Gb SFP+
USB 2 2xUSB2.0 5(2 front,2 rear, 1intrl) 2 front USB3.0, 2 Rear USB 3.0 and 1 internal 2 front USB3.0, 2 Rear USB 3.0 and 1 internal
USB (secure) USB (secure)
Console 1 (RJ-45) Cable included 1 (RJ-45) Cable 1 (DB 9 - Male) No No
included
VGA No No Yes 1 video port in front, 1 video port in rear 1 video port in front, 1 video port in rear
Replaceable Hard Drive No No Yes Yes Yes
Redundant PSU No No Yes (350W) Yes hot pluggable ( 750W) Yes hot pluggable (750W)
N/A iDRAC Exp – dedicated port iDRAC Exp- dedicated port
Management N/A N/A
1U (Desk or Rack Mount) 1U 1U 1U
Form Factor
Power
100/240V AC Adaptor 100/240V AC Adaptor 100-240V AC 50/60Hz 100-240V AC 50/60Hz 100-240V AC 50/60Hz
Input (12V DC) (12V DC)
AC Power (Max) 40 Watts 24 Watts 300 Watts 750W 750W
Environmental
Nominal Operating Temp 20oC 20oC 20oC 20oC 20oC
Operating Temp Range 5oC ~ 40oC 5oC ~ 40oC 10oC ~ 35oC 10oC ~ 35oC 10oC ~ 35oC
Relative Humidity 20% ~ 90% 20% ~ 90% 20% ~ 80% 20% ~ 80% 20% ~ 80%
(Non-
Condensing)
Storage Temp 0oC ~ 75oC 0oC ~ 75oC -40oC ~ 65oC -40oC ~ 65oC -40oC ~ 65oC
Certifications & Compliances FCC, CE, UL & RoHS FCC, CE, UL & RoHS FCC, CE, CSA, UL & RoHS FCC, CE, CSA, UL & RoHS FCC, CE, CSA, UL & RoHS
3.3.3.2IP Office / Mid-Market

The Hardware appliance offering for Mid-market/IP Office is more limited than the enterprise selection
described above 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 (CSR3 and ASP based) and Hi-Cap with accelerator (CSR3 and ASP
replacement) are not available for the Mid-market/IPO segment thru IPOSS.
Specification Low Range ASBCE Mid-Range ASBCE

Portwell CAD 230 Portwell CAF 251 Dell
Product Type ASBCE CORE/EMS ASBCE CORE/EMS ASBCE CORE/EMS
Part Number 388052/388053 700515001 388048/388049
Platform Type CAD-0230-4611 CAF 251 PE R330 (CSR3 OEM)
Life Cycle 36 months 36 months 18 months
BIOS R1.01 (Avaya only) Standard TBA
Intel Celeron N3350, 2C Xeon E3-1220 v5- 3.0 GHz
Processor ATOM C2358 – 1.7GHz (2M Cache, up to 2.4 GHz) (4 cores - 80W)
2GB DDR3L 1333MHz SODIMM DDR3L 4GB on board 8GB (2X 4GB) DDR4
Memory 2133MT/s ECC UDIMM
RAID No No RAID 1
Hard Drives 500GB (SATA) 64GB SATADOM,Innodisk 2 X 300GB 10K (SAS)
64GM41BC1SCA -H82
+ EMMC 4GB onboard
Optical Drive No- No DVD+/-RW
Compact Flash No- No No
Quad 1GbE Port NIC PCIe-4 (Intel 1350 QP)
PCIe Cards No- No
Specification Low Range ASBCE Mid-Range ASBCE

Portwell Dell
TPM No No No
LCD/LED Display No No Yes
Interfaces (Ports)
Data 6 X 1GbE 4X 1GbE 6 X 1GbE
USB 2 2 5(2 front,2 rear, 1intrl)
Console 1 (RJ-45) Cable included 1 (RJ-45) Cable included 1 (DB 9 - Male)
VGA No No Yes
Replaceable Fan No No Yes
Replaceable Hard Drive No No Yes
Redundant PSU No No Yes (350W)
Port Bypass No No No
N/A N/A
Management N/A
1U (Desk or Rack Mount) 1U (Desk or Rack Mount)
Form Factor 1U
Bezel - No
Dimensions
Height 1.7 in (43mm) 30mm 1.7 in
Width 8.27 in (210mm) 180mm 17.1 in
Depth 8.27 in (210mm) 130mm 24
Boxed
Height 7.5 in 10.5 in
Width 12 in 24 in
Depth 15 in 35.5 in
Weight
Unit 3 lbs. 1.14Kg 25 lbs.
Boxed 6 lbs. 48 lbs.
Power
100/240V AC Adaptor (12V DC) 100/240V AC Adaptor (12V DC)
Input 100-240V AC 50/60Hz
Nominal Current (110V) 0.2 A 1.36A
Maximum Current (110V) 0.5 A 2A

AC Power (Max) 40 Watts 24 Watts 300 Watts
Calculated Power Consumption
22Watt/75BTU 150W/512BTU
Environmental
o o
Nominal Operating Temp 20 C 20 C 20oC
Operating Temp Range 5oC ~ 40oC 5oC ~ 40oC 10oC ~ 35oC
Relative Humidity (Non- Condensing)
20% ~ 90% 20% ~ 90% 20% ~ 80%
Storage Temp 0oC ~ 75oC 0oC ~ 75oC -40oC ~ 65oC
Certifications & Compliances FCC, CE, UL & RoHS FCC, CE, UL & RoHS FCC, CE, CSA, UL & RoHS
3.3.4 Discontinued Hardware appliance with Release 8

Due to the level of performances required by the Release 8.0 of the ASBCE software and the impact on older hardware
performances that the specter/meltdown fixes introduce, the following hardware appliances are no longer supported with
ASBCE Release 8.x (since 8.0) for both the enterprise and IPO/Mid-market segments:

- CAD208 based appliance
- R210 based appliance
- R210-II based appliance
3.3.5 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 and One Cloud offers.
It is also the Avaya recommended ASBCE for the Powered By IPO offer addressing the mid-market needs.
The ASBCE is 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 IPO Powered By partners – Refer to Powered By offer definition, 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.1.1.
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
Release 8.1.1 does bring two major cloud related enhancements with :
- Support for SBCE HA while deployed in AWS
- Simplex deployment in Microsoft Azure
-
The software packages available for these environments are specific for each environment and are available
and tracked under separate material codes as can be seen in this section of this document.
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, AWS and Azure) for more details.
3.3.6 Discontinued Virtualization platform support with Release 8

As the virtual machine version of the OVA released with ASBCE 8.0 had to evolve to version 11 to support the specter /
meltdown fixes efficiently, the following virtualization platforms are no longer supported with ASBCE Release 8.0 and
Release 8.0.1 and Release 8.1 for both the enterprise and IPO/Mid-market segments:
- vSphere 5.0
- vSphere 5.1
- vSphere 5.5

4 ASBCE 8.1.1
4.1 Overview
These various evolutions cover a broad range of potential solutions and applications:
• ASBCE is the only fully stack-tested SIP security application for the Avaya communications
environment. Solutions for both Edge Security and enhanced Core Security are delivered by this
application. This testing is accomplished via Avaya software development programs and Solution &
Interoperability Lab (SIL) testing, GSSCP testing, etc. ASBCE is the only ASBCE consistently tested
in these processes.
• SIP Trunking and customer migration away from TDM trunking to SIP continues as a major driver
for implementation of SIP-based Unified Communications. ASBCE supports, with the family of
platforms offered, broad scaling for SIP trunking from as few as 5 to as many as 30,000 simultaneous
sessions. All Avaya core Call Server environments are supported (CM, IP Office, CS1000), and Call
Center and OneCloud/xCaaS environments are supported as well. ASBCE also supports SIP
trunking for third-party call server environments (Cisco, ShoreTel, Mitel, Microsoft Skype for
Business) Application notes with details about setup/testing are also available on the Sales and
Support Portal.
• Avaya ASBCE supports the macro trends in the market for the Mobile work force and the growth of
Cloud-oriented offerings with the VPN-less Remote Worker capabilities of the ASBCE. Mobile
workers outside the firewall and users of hosted Cloud offers with Avaya Clients can be securely
integrated to the Aura core via connection through ASBCE. ASBCE is the session border controller
leveraged for Avaya Mobile Experience. More information about Avaya AME available on the sales
portal.
4.2 Business Partner Value Proposition

4.2.1 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.
4.2.2 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.
4.2.3 Defensible Differentiators
Avaya ASBCE is the flagship UC/CC edge security solution from Avaya and incorporates the following
Defensible Differentiators:
• High availability and security – The in-depth multi-level redundancy, fail-over and survivability
capabilities of Avaya ASBCE delivers true enterprise grade reliability
• Solution designed with security at the core - The security, encryption, and software “hardening”
provided at every level across all aspects of ASBCE provides a unique differentiator. ASBCE has
met the highest level of standards as defined by the US Defense Information Systems Agency (DISA)
to pass JITC certification in September 2017( new certification expected in June 2020) and be listed
on the US Department Approved Product List (APL), joining a group of select few able to reach this
extremely rigorous, independent and significant accreditation.
• Focus – Avaya is focused on the Enterprise Communications Business User with an unswerving
focus on meeting the communications needs of business users in all roles and organizations.
• Avaya Remote Worker: Avaya SBCE is the Sole session border controller in the market enabling
and supporting the Avaya Remote workers full suite of functionalities. Despite Oracle claims, and
based on Avaya proprietary PPM protocol and Avaya proprietary SIP extensions implementation,
any Avaya soft or hardware endpoints deployed in a VPN less remote worker mode will require the
use of SBCE in order to deliver its complete range of UC &/or CC features.
• The reference SBC used as the network Edge for Ready Now Private Cloud and Equinox Meeting
Online: ASBCE has been considerably enhanced as of Release 8.0 to provide improved robustness
(support for Edge Browser) and scale to WebRTC calls with any Equinox deployment (cloud or on
premise).
• Contact Center strength – Avaya is the global market share leader in contact centers, powering tens
of thousands of centers and millions of agents worldwide. ASBCE is a key foundation to secure these
infrastructures as they evolved to SIP, enabling secure remote access to the expanded capabilities
of Avaya Aura and contact centers offerings which are now powering innovative new customer
service solutions serving millions of customers everywhere. Additionally, ASBCE 8.0 introduce RFC
based SIP Call path restoration in conjunction with Aura 8.x to provide large Avaya SIP based contact
centers the resiliency and reliability they expect and should require from their enterprise grade UC &
CC solution.
• Open and standards-based – Avaya remains committed to true open standards support and multi-
vendor interoperability. Despite the claims of many vendors, Avaya shows this in practice and truly
provides the benefits of open systems to customers. Strong certification and interoperability with
Microsoft UC ecosystem such as SFB 2016 and Teams are living proofs of this open standard
support commitment.
• DevConnect ecosystem – Avaya has the most comprehensive developer ecosystem in the
communications space, providing a broad range of choices for customers (understanding that
Microsoft and IBM do bring very strong developer capabilities from their spaces that Avaya can

complement).
• Backed by extensive professional, support and managed services – Avaya and our Business
Partners have the industry’s most extensive array of services focused completely on enterprise
communications. We help customers get it done.
4.2.4 Partner Business and Strategic Value

4.2.4.1Enterprise Use Cases
ASBCE release 8.1.1 solutions provide a unique and powerful edge control solution to business customers
with Aura, CS1000, and IP Office customers (as well as supporting 3rd party call servers). A range of use
cases for this GA introduction of Avaya ASBCE 8.1 include
• SIP trunking to Carrier networks from Aura configurations, Communications Server 1000 (CS1K),
and IP Office.
o The Enterprise customer is evolving from TDM trunking to SIP trunking to carriers/PSTN,
and this use case is the largest in terms of volume in the current market.
o SIP trunking to Carrier networks from IP Office 9.1 (and higher). The SME customer is
evolving from TDM trunking to SIP trunking to carriers/PSTN, and this use is fully supported.
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.
o Introduced as of release 7.2, ASBCE now supports IPv6 on Enterprise side for SIP Trunking.
This is covered within the Standard Service license.
o Introduced as of release 7.2, Trans-rating. This is covered within the Transcoding license.
o Introduced as of release 7.2, dynamic licenses.
o Introduced as of release 8.0, support for Avaya Converged Platform granting higher
scalability at a lower cost
o Introduced as of release 8.0.1, the CAF 251 offers the most cost-effective hardware
appliance solution for SMB looking for up to 100 concurrent sessions of SIP trunking and
Avaya Remote workers.
• Remote Workers in a VPN less and/or Full SIP 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 +Advanced Service license.
o Increased resiliency, improved redundancy and scalability for WebRTC call with Equinox on
premise and Cloud deployments.
o Due to the constant evolution of Avaya advanced protocols for endpoints management PPM

and advanced SIP features AST-II, ASBCE is the only session border controller in the
market enabling and supporting the Avaya Remote workers full suite of functionalities
• Bring Your Own Device security (BYOD) and additional network SIP-VoIP security: Many customers
in the Enterprise have needs for securing the IP-PBX core at a higher level and need to securely
manage SIP-VoIP endpoints ‘homing’ to the Enterprise Aura core. ASBCE 8.0.x supports this need
with Advanced Services that include validation of users and encryption of signaling and media in
environments with back-to-back or back-to-back-to-back ASBCE implementations with the Aura
infrastructure.
• 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. License (397222) is required for remote SIP video room system endpoints
that need to connect into Equinox Conferencing through firewall via ASBCE, share content
and control cameras remotely.
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
• Secure Edge for Avaya OneCloud – as the enterprise adopts Avaya OneCloud, deployment of Avaya
SBCE at the locations where users concentrate enables higher level of security between the
locations and local tail end hop off
• Interoperability with Microsoft Unified Communication suite: with ASBCE Release 8.1.1, Avaya Aura
customers can now integrate their SFB2016 or Microsoft Teams domains with their Avaya domain,
enabling audio calling between the two domains. ( note: additional licenses may be required on the
Microsoft side to enable the inter domain calling feature)
4.2.4.2 Mid-market Use Cases

The Mid-market offers based around the Avaya IP Office platforms leverage the same Avaya ASBCE
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 Mid-market and cross-BU testing for delivery support.
ASBCE release 8.0.1 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.1 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
• Introduced as of release 8.0.1, the CAF 251 offers the most cost-effective hardware appliance
solution for SMB looking for up to 100 concurrent sessions of SIP trunking and Avaya Remote
workers.
• Interoperability with Microsoft Unified Communication suite: with ASBCE Release 8.1.1, Avaya
IPO customers can now integrate their SFB2016 or Microsoft Teams domains with their Avaya
domain, enabling audio calling between the two domains. (note additional licenses may be
required on the Microsoft side to enable the inter domain calling feature)
4.2.5 Avaya Support for Go-to-Market

Avaya support for go-to-market includes extensive sales training and knowledge transfers, comprehensive
sales collateral, access to the DevConnect Program, support for demonstrations, partner and customer
events and ad hoc engagements as required.
The latest Technical Transfer (higher level) and Knowledge Transfer (more in-depth technical content)
recordings can be found at:
Release 8.0:
Webcast Title: Tech Transfer - Avaya Aura 8 Architectural Improvements and Enhancements
(includes the SBCE 8.0 TT)
Webcast Date: Wednesday, January 16, 2019 at 11:00 AM Eastern Standard Time
Audience URL:
Use this link to access the audience view of the webcast.
https://event.on24.com/wcc/r/1907737/C2A2C81560C48BDA42EC8FD3CDE96EA7
Webcast Title: ASBCE 8.0 pre-GA-KT

Webcast Date: Tuesday, January 29, 2019 at 09:00 AM Central Standard Time
Audience URL

https://event.on24.com/wcc/r/1922806/D391400447A202330F0B8AC2783EB4E0
Release 8.1:
Webcast Date: Tuesday, January 14th, 2020 at 09:00 AM Central Standard Time
Use this link to access the audience view of the webcast.
https://conferencing.avaya.com/portal/tenants/default/recording/?ID=ab402fb2a14449a1857bc10020b8e283
Release 8.1.1:
Webcast Date: Monday, July 20, 2020
Audience URL
https://conferencing.avaya.com/portal/tenants/default/recording/?ID=f3d6e35412d943e29d90c4e51da91a0a
The latest sales presentations for SBCE 8.0, SBCE .8.0.1, SBCE 8.1 and SBC 8.1.1 are also available online
on the Avaya Sales portal at the time of the publication of this document
.
5 ASBCE 8.0, 8.0.1, 8.1 and 8.1.1 Feature descriptions

Even though ASBCE R8.x release train primary theme and focus have been to simplify the user experience,
the release delivers several additional key 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
• Improved cost effectiveness for SMB with new low-end appliance (CAF251) introduction [8.0.1]
• Microsoft Skype For Business certification for 8.x release train [8.1]
• Overall UC solution TCO improvements [8.0.1]
• GDPR compliance [8.1]
• CCPA compliance [8.1]
• JITC Certification [8.1]
• Support for R340 mid-size appliance [8.1]
• Multi-destination SIPREC [8.1]
• Frequent Security Patches support [8.1]
• URN invite for NG911 [8.1]
• URN mapping-basic call for NG911 [8.1]
• FQDN/DNS SRV registration with ITSP [8.1] & [8.1.1] (for ITSP offering this feature)
• IPV6/ANAT support for integration with CSDK 4.3 [8.1]
• Dynamic licensing Support for Mid-Market [8.1]
• Support for SBCE HA in Amazon Web Services (AWS) [8.1.1]
• Simplex deployment in Microsoft Azure [8.1.1]
• Microsoft Teams certification for Direct Routing with no Media Bypass [8.1.1]
5.1 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.x focus has been to deliver the necessary improvements
in this area
5.1.1 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.
5.1.2 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
5.1.3 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
5.1.4 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 3rd 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.
5.1.5 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.
5.1.6 Reverse Proxy using TLS Server Name Indication (TLS SNI) [8.0.1]
From the previous release, Multi Tenancy Service enables secure sharing of a single public IP of ASBCE
across multiple Tenants/Customers. However, the multiple tenant’s solution roll out was cumbersome and
sometime simply impossible, due to the complex certificates and reverse proxy configurations required
With this enhancements ASBCE solves serving a tenant certificate to the client and route to an appropriate
IPO/Server based on received TLS SNI. This greatly simplifies the multitenant configuration for IPO and
avoids having to combine all tenant certificates into a single one. From Release 8.0.1, ASBCE serves only
requested tenant certificate to the client.
For the reverse proxy, a new drop down is now introduced in the EMS offering the option to select an option
called received server host enabling the SBCE to leverage the TLS SNI function for a tremendously improved
configuration experience.
5.1.7 Removal of Volume Tiered pricing for a simpler ordering experience [8.0]
Starting at the General Availability of ASBCE 8.0 on February 11th 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.
The new pricing for these licenses is described in the pricing section of this document
5.1.8 SNMP alarming when ASBCE is nearing session saturation [8.0]
ASBCE generates a new SNMP alarm when ASBCE is nearing 80% of the call leg capacity of the system.
5.1.9 Deployment Automation & Configuration API [8.1]
In R8.1, a set of RESTful APIs designed for deployment automation and configuration has been introduced.
APIs are fully authenticated, and all APIs are secured through TLS channel.
These APIs use a cloud friendly architecture based on the Springboot framework, and support Create
(POST), Get ALL (GET *) Get (GET), Delete (DELETE) and Update (POST with subset). This interface
validates the data and when relevant, returns error codes with error message and reason of errors
APIs are also provided for logging and Alarming.
The design of these APIs is intended to allow the SBCE to be managed by 3rd party management system
and/or provide simplified user experience via EMS.
Non-EMS, management solution support from Avaya will be announced by the corresponding Avaya
product(s) upon successful integration against SBCE management APIs.
RESTful APIs configuration APIS schema have been released via our DevConnect program.
5.1.10 Manageability via Equinox iView [8.1]
The Configuration APIs in Release 8.1 have been designed to ensure that the Equinox conferencing
management server, iView, can be used instead of the EMS for Equinox conferencing related
configuration.
The Equinox solution is responsible for announcing the availability of this integration and what release of
iView is required to support this feature.
In any case, EMS will still be required for installation and upgrade and fine tuning of configurations
5.1.11 SIP, TURN, PPM and HTTP logs in EMS [8.1]

SIP, TURN, PPM and HTTP logs were available In the SBCE trace SBC logs only prerelease 8.1 – As of
R8.1, all of the logs in question are now available in the log section of the EMS GUI.
5.1.12 Support for FQDN/DSN SRV registration [8.1]
Certain ITSPs require Session Border controllers to register to their services prior to processing any call –
this registration leverage fully qualified domain name for improved manageability and DNS-SRV is used
by the ITSP to help provide redundancy in their implementation.
Via DNS-SRV, the SBCE after detecting failure (leveraging OPTIONS messages), the SBCE can
unregister and register with the next priority server.
SBCE does not support load balancing and selects only one priority server for registration.
5.1.13 Dynamic Licensing for Mid-market [8.1]
As of Release 8.1, dynamic licensing is now available for purchase for mi-market solution.
5.1.14 Support for Security only patches [8.1]
As of Release 8.1, the EMS is now allowing patches to be applied from the GUI like Service Pack previously
were. The SBCE R&D team will be issuing security only patches in compliance with Avaya security
guidelines which provides guidelines in term of fix delivery timing for P1, P2 and P3 security issues which
can be found at https://downloads.avaya.com/css/P8/documents/100045520
5.2 Better Together with Equinox
Release 8.0 continues to solidify and improves the existing integration between ASBCE and the Equinox
solution.
5.2.1 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.
5.2.2 Greater Turn capacity for WebRTC client aka Increased Media Tunneling
capacity [8.0]
The Turn server in the SBCE 8.0.x 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.
5.2.3 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.
5.3 Better integration for SIP contact center with Aura
Prior to Release 8.0, ASBCE supported Call Path restoration following the Avaya proprietary FGDN method
in alignment with Aura 7.x and 8.x implementation. (application note can be located here ).
With the general availability of Aura 8.0 an additional standard based implementation has now become
available. The two features described are in support of this implementation FQDN based starting with Aura
8.0.
5.3.1 Support for Extended host name validation [8.0]
ASBCE 8.0.x now supports Extended Host Name Validation, which is validating the host name of the server
in the identity certificate presented by server during TLS handshake. This is required to prevent man-in the-
middle attacks but also to support the implementation of the new standard based SIP Call preservation
feature introduced with Aura 8.0.
5.3.2 Support for Call preservation [8.0]
To ensure the signaling path and media stream are restored in case of a Session Manager failure, Aura 8.0
will add support for SIP call reconstruction at the SIP signal layer. This will allow mid-call features to be
executed by users after the call has been re-constructed. ASBCE is required to understand this new standard

based (FQDN) implementation in Aura 8.0 in order to deliver end to end SIP Call preservation.
5.3.3 Multi-destination SIPREC [8.1]
Prior to release 8.1, SBCE could fork the current session up to only one destination via SIPREC. With the
introduction of this feature, the SBCE can now fork the same media streams up to 4 independent destinations.
Each media stream can have independent policies in term of selective or full-time recording,
unencrypted/encrypted etc.
All of the functionalities previously supported for a single recorder solution including HA, selective recording
and load balancing within a recording pool are applicable and supported with the Multi destination SIPREC
feature.
This feature has been designed specifically to cater to the media processing needs of advanced contact
center allowing for instance parallel recording, rea time transcription, biometrics and sentiment analysis of
one caller.
The SIPREC destinations could be all on premise behind the firewall or in the cloud, or a mix of both.

Additional advanced licenses are required for access to additional SIPREC destination – please check the
advanced licensing section of this offer documentation for more details.
5.4 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
5.4.1 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
5.4.2 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.
5.4.3 Microsoft Skype For Business certification for 8.x release train [8.0.1]
Starting from release SBCE 8.0.1 and for the rest of the SBCE 8.x release train, Microsoft has tested and
certified the SBCE against its Skype For Business on premise offer. Since the official certification program
from Microsoft Skype For Business has ended to the profit of Microsoft Teams certification, Microsoft will be
issuing a letter of conformance and support to Avaya stating that the SBCE 8.x is recognized as supported
session border controller device against Skype For Business on premise. This statement of compliance is
not available at the time of this document issuance and is expected to be released by Microsoft later in the
quarter. This section of the offer definition will be updated when this generic support statement becomes
available.

5.4.4 Microsoft Teams certification for Direct Routing with no Media Bypass
[8.1.1]
As of release 8.1.1, ASBCE is certified for Microsoft Teams Direct Routing with no Media Bypass.
This certification of interoperability allows a customer to integrate their Microsoft Teams domain with their
Avaya domain and enable audio calling between the two domains.
This means that a MSFT Teams client is now able to place/receive audio calls to/from a trunk (SIP or TDM)
on the Avaya systems and to place/receive audio calls to/from an Avaya endpoint (SW or HW). More details
can be found in relation to this integration and the features supported in the new document “Working with
Microsoft Teams” now part of the SBCE library on the Avaya support web site.
Notwithstanding additional licensing requirement on the Microsoft side to enable Calling between the two
domains, access to this feature on the ASBCE will require the purchase of a Premium license on SBCE (
new feature tier introduced in 8.1.1) – please refer to the licensing and pricing section of this document for
more details in regard to the Premium licensing.
The certification is officially recognized by Microsoft and entitles any Avaya -Microsoft joint customer under
relevant support contract, to contact either organization to seek and gain support in regard to any technical
issues related to this integration. In other words, the certification is the official recognition that this
interoperability is supported by both organizations.
5.5 Overall UC solution TCO improvements [8.0.1]
5.5.1 Support for Shared AAMS instance [8.0.1]
From prior SBCE releases, Aura Media Server (AAMS) was usable by the SBCE in order to provide high
capacity transcoding and trans-rating functionality.
As of Release 8.0.1, ASBCE able to share the stand alone AAMS instances which are also shared by other
adopters in the solution. Customers will be able to use one media server for their entire solution reduces
footprint, power and cost. An already existing AAMS can be leveraged by SBCE (i.e. not requiring the
deployment of a brand new one)
Cloud deployments are also becoming more cost effective with common media servers as the resources are
homogenous, pooled and shareable.
5.5.2 Preloading of trust for Avaya Device Enrollment Services [8.0.1]
With SBCE 8.0.1, the SBCE out of the box software will be pre-loaded with Avaya Device Enrollment Services
Certificate Authority trust.
Since J1xx and Vantage supports DES, this preloading will facilitate the rollout of remote J1xx and Vantages
devices when high level of authentication (MTLS) is required between the SBCE and the endpoint.

5.6 Technology currency & Security
5.6.1 Avaya Security Common Engineering Criteria compliance [8.0]
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
5.6.2 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, Vantage K155 and J1XX
series – Vantage K175 does not support this feature at this time)
5.6.3 Logging CEC compliance [8.0.1]
To follow Avaya’s engineering best practices in regard to logs management, Events, Log transmission and
log format, several enhancements have been delivered in SBCE 8.0.1.
SBCE now supports logging all the events generated by its different software processes (SSYNDI, ICU,
AUDIT, GUI, Linux OS) to a common syslog server.
With Release 8.0.1, SBCE records the date and time of log in and log out, each login to the system console,
a sequential entry for every command, restart, reboot, and initialization, any components removed from
service and restored to service, system console messages, utilization limits the status information about an
application or process upgrade and update progress messages entries in system event log(s).
SBCE application and audit logs provide an information about a summary of tasks performed and change
history, by user profile and type and noting any parameter changed. All the SBCE events will include the

logging ID, time/date, and nature of the change. Such events are especially useful in a shared management
environment for tracing event history when undesirable situations occur. ASBCE is maintaining logs on
remote machines is a technique used to discourage attack by requiring an attacker to access multiple
systems in order to remove their activities from log files. ASBCE provides remote logging for a central security
information management and this logging is done following RFC 5424 (SYSLOG protocol) and RFC 3195
(Reliable Delivery for syslog) in lieu of RFC5424. Log files may wrap-around and overwrite existing data in
the memory cache area.
All the audit logs are stored in /var/log/audit directory on the system. These logs can be stored in remote
server. There are now specific set of tools available to verify and read audit logs.
5.6.4 JITC compliance [8.1]
Release 8.1 has been designed to meet all of the SBC requirement of the UCR 2013 as defined by the US
DOD. At the time of the issue of this document, SBCE 8.1 is undergoing the accreditation process by the US
DOD DISA department. Once granted this section will be updated to reflect the actual certification and a link
will be provided to the DISA Approved product list.
Since Release 7.1.0 was the prior JITC release, a direct upgrade path exists between 7.1 to 8.1
Refer to the SBCE Military Unique Deployment Guide (MUDG) for further details on how to configure the
SBCE in JITC mode.
5.6.5 GDPR/CCPA compliance [8.1]
GDPR compliance regulates privacy and protection of personal data. SBCE as a call processing and media
device has transient media and call signaling data which does not require GDPR compliance.
GDPR compliance for SBCE has primarily to do with data at rest – the data which may contain PII are:
- CDR
- Runtime Tracing
- Debug Logs
Compliance for CDR is achieved by leveraging Radius server is one is in place or SFTP transmission of CDR
file.
Compliance for Debug logs is done by only transmitting the logs over SFTP or secured channel using TLS.
The debugs logs are only readable with root access on the SBCE appliance.
Finally, compliance for runtime tracing is achieved by anonymizing all user data and file are transmitted over
SFTP or secured channel using TLS. SBCE provides utilities to decrypt and read the anonymized files on
the log server.
5.6.6 Two Factor Authentication for Privileged Users [8.1]

As for Release 8.1, SBCE supports X.509 user certificates for authenticate SBCE administrators aka
privileged users.
This certificate-based authentication is what is used in release 8.1 to provide a two-factor authentication
For JITC environment, a supplicant software requiring the user to enter a PIN ( what you know – the first
factor ) is used to extract the X.509 certificate out of the CAC card ( what you have – the second factor)
inserted in the laptop – this certificate is then presented to SBCE EMS for mutual authentication.
In a typical commercial environment, the PIV/Smart card is used the entered username & password for a 2-
factor authentication.
5.6.7 Single Sign on for Privileged Users [8.1]
LDAP support for Single Sign On has now been introduced with Release 8.1 for all customers – JITC and
Commercial.
Similar to the Radius implementation, the feature requires local user creation to map LDAP users to SBCE
role.
This feature has been tested against MSFT Active Directory and Apache Directory and is stated as supported
against any LDAP compliant server.
This single sign on fully support TLS & SSL encryption.
5.7 Next Generation 911
As the emergency services in the US and Canada are awakening to the need of modernizing their current
telecommunication infrastructure supporting 911, new standards have emerged to support this initiative: it is
called NG911 or Next Gen 911.
In this new model, a Session Border Controller or SBC interacts with the NG911 core services providing the
NG911 functionality. The selection of the proper NG911 PSAP as well as the emergency call initiation
leverages a new type of URI – URN – Unified Resource Name – which is handled by the NG911 Core
services and passed along to the SBC for processing at the PSAP level.
5.7.1 URN invite [8.1]
The SBCE Release 8.1 is now able to parse and process URN invites for basic call and Hold/Un-hold flows.
5.7.2 URN Mapping [8.1]
URN Maps are used for Emergency and other well-known services. It avoids usage of dialed digits and
routing conflicts which could arise from it. For the NG911 case, URN Maps are used for Emergency call
service. It abstracts locations and regions, and SBCE converts URN map from a specific location and region
to actual emergency dialed digits

5.8 Platform support
5.8.1 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.
5.8.2 ASP Hardware appliances [8.0]
ASBCE Release 8.0 is the first ASBCE release to support the ASP 110 Profile 3 and ASP 110 Profile 5
hardware appliances.
5.8.3 Improved cost effectiveness for SMB with new low-end appliance (CAF251)
introduction [8.0.1]
ASBCE Release 8.0 1is the first ASBCE release to support the Portwell CAF251 low end hardware appliance.
This brand-new appliance is positioned to be roughly half of the price of the CAD230 and provides up to 100
mac concurrent sessions as a combination of SIP trunking and Avaya remote workers (hardware or software
endpoints) to server the lower end of the SMB market where the CAD230 is not competitive. HA, Transcoding,
SIPREC and Scopia remote hardware endpoints are not supported with the CAF251.
5.8.4 Support for Avaya Virtualization Platform [8.0.1]
Equally as fundamental as new low-end appliance platform support, ASBCE Release 8.0 1is the first release
to support deployment onto the Avaya Aura Virtualization Platform aka AVP.
AVP is the Avaya hypervisor layer running on all Avaya provided hardware appliance ACP120, and prior to
that the Common Server Release 2 and 3 (CSR2 and CSR3).
As of Release 8.0.1 of the SBCE and Release 8.1 of Aura (i.e. AVP 8.1 and Solution Deployment Manager
-SDM 8.1), the SBCE application can be deployed on top of an AVP appliance using the SDM client only.
Support for the SDM embedded client in SMGR for deployment of SBCE on AVP will require SMGR release
8.1.1 at a minimum.
Only server-based appliance ie CSR2, CSR3 and ACP120 are supported by the SBCE when SBCE 8.0.1 is
running on top of AVP. Deployment of SBCE 8.0.1 on top of AVP running in a 8300e embedded blade is not
supported at this stage.
In SBCE 8.0.1 and Aura 8.1, The EMS function can be deployed in Shared AVP mode, meaning that the
EMS can share an AVP appliance with others Avaya Aura application on the same AVP. The SBCE function
on the other hand can only be deployed in dedicated AVP mode meaning that the SBCE application is the
only application running on top of this AVP appliance.
The SBCE 8.0.1 supports hybrid type of deployments inclusive of AVP, which translates into EMS could be

deployed and run on top of AVP while SBCE applications could be running on top of AVP or VE or dedicated
hardware appliances.
The Avaya One Source configurator will be updated post SBCE 8.0.1 GA in the September issue of the tool
to support SBCE configuration on AVP.
5.8.5 Support for Dell R340 – new mid-size appliance [8.1]
A new mid-size appliance has been introduced from Release 8.1 and will progressively replace the R330 as
its stock depletes. This new mid-size appliance will support the same capacity as the R330.
5.8.6 Support for SBCE HA in Amazon Web Services (AWS) [8.1.1]
With SBCE Release 8.1.1, the SBCE can now be deployed in AWS in HA mode. Amazon has worked with
Avaya to adapt its environment and provide enhancements to better support the GARP mechanism, which
is the mechanism used by SBCE to perform HA failover.
Even though the HA failover is not as fast as in a traditional appliance or VE type of environment ( which is
typically in the sub second range in these environment) where the customer is in full control of the deployment
and network, the performances have been deemed satisfactory to meet our customer expectations in term
of HA failover. These failover performances are however varying depending on the type of connection one
will select to connect its network and AWS cloud.
The HA failover performances are however different than on standard VE appliances.
If the connection between the Customer network and AWS cloud is VPN based then the HA failover
performances are in the range of 2-5s, meaning that during an SBCE HA failover the current active
calls will be maintained but the audio will be disrupted for 3s mean, 5s. worst case.
If the connection between the Customer network and AWS cloud is over the internet ( i.e. not VPN
based ) then the HA failover performances are in the range of 8-12s, meaning that during an SBCE
HA failover the current active calls will be maintained but the audio will be disrupted for 8s mean, -
12s. worst case. Even though our tests in lab have never demonstrated audio disruption for longer
than 8s, Amazon SLA indicates that the disruption could last up to 12s worst case.
5.8.7 Simplex deployment in Microsoft Azure [8.1.1]
Also, with Release 8.1.1, SBCE can now be deployed in Azure in Simplex mode only (No SBCE HA support
in SBCE 8.1.1 for deployment in Azure).
A new Virtual appliance material code has been created and made orderable for such deployment - purchase
of this material code will grant access to the right SBCE packaging download in PLDS. The pricing for the
Azure SBCE packaging is the same as for all other virtual appliances – please refer to the licensing / pricing
section of this document for more details.
A procedure will be provided for generating the VHD (proprietary Azure packaging) from the SBCE packaging
offered in PDS. At the time of publication of this document, the option to download the VHD directly from
PLDS is not offered due to the file size( ~80G+).

To the exception of SBCE HA, all SBCE functionalities are supported in Azure with the version 8.1.1.
6 Upgrading to ASBCE 8.1.1

Current ASBCE customers are strongly encouraged to upgrade to the new release to retain the full value of
their security investment and gain access to the features and functionalities of release 8.1.1.
To simplify customers’ migration to the latest and most secure release of the ASBCE, several direct upgrade
paths from R7 are available and fully supported.
The upgrade from release 7.x to release 8.x is a major release upgrade, different from previous releases of
ASBCE. As Avaya ASBCE is now integrated into Avaya’s tools (ASD, PLDS, etc.), upgrade procedures are
generally aligned with the rest of the Aura core processes.
• Customers who have purchased Upgrade Advantage as part of their Support Advantage
Maintenance will leverage the Entitlement codes (see this section ) via the suite of Avaya Sales
tools, and the upgrade is no charge.
• Customers not under an Upgrade Advantage contract will use ASD to support their upgrade and
leverage the Upgrade codes that charge a fee for upgrading release 7.x software to release 8.x
software
Customers wishing to expand capacity of their release 7.2.x systems may do so simply within the release
7.2.x product structure as session capacity for the system can be added by ordering more sessions via A1S.
Commercial customers running Release 7.x should ensure they upgrade their SBCE to release 7.2.2 which
is the Release 7 EMSSP for SBCE.
As a prenotice, SBCE R7 is about to start Sunsetting as SBCE R8.1 reached the DISA APL and was
announced as the new SBCE EMSSP.
JITC customer running Release 7.1 should upgrade to the latest service pack (7.1.0.9 at the publication of
this document) prior to upgrading to release 8.1which is now listed on the DISA APL as of June 2020.
Customers on release 6.x are required to upgrade to the latest GA release prior to executing any expansion
since R6.x has gone End of manufacturing Support since August 2019.
Upgrading from Release 6.3:

Customer will be required to upgrade first to Release 7.2.2 from 6.3.x – please refer to ASBCE offer Definition
Release 7.2.2 for more details.
Upgrading from pre-release 6.x

Please contact Avaya Product Operations (productops@avaya.com).
6.1 Upgrade IPOSS customers from ASBCE 7.x to 8.1.1

Please note the following process:
• Check and validate the IPOSS contract number and the Sold-to where the ASBCE licenses are

present in PLDS.
• Check the ASBCE R7 codes for IPO and create the equivalent ASBCE R8 codes for IPO in PLDS
from the mapping list below
R7 Codes R8 codes
382300-ASBCE R7 STANDARD 397232- ASBCE R8 STD SVCS
SERVICES SESSION IPO LICENSE 1- IPO LIC
500
382301-ASBCE R7 STD SVCS IPO LIC 397232- ASBCE R8 STD SVCS
501-1000 IPO LIC
382305-ASBCE R7 ADVANCED 397237- ASBCE R8 ADV SVCS
SERVICES SESSION IPO LICENSE 1- IPO LIC
500
382306-ASBCE R7 ADV SVCS IPO LIC 397237- ASBCE R8 ADV SVCS
501-1000 IPO LIC
382329-ASBCE R7 ENCRYPTION FOR 397261- ASBCE R8

IPO LICENSE ENCRYPTION FOR IPO LIC
6.2 Supported upgrade paths to ASBCE 8.1.1
The following software direct upgrade paths to ASBCE R8.1.1 are supported:
- 8.0.1->8.1.1
- 8.0->8.1.1
- 7.2.2.x(7.2.2.2 & 7.2.2.3)->8.1.1
- 7.1.SP4, 7.1.SP9 (JITC only)->8.1.1
The following Indirect upgrade paths to ASBCE R8.0 are supported:

- 6.3.x -> 7.2.2.x -> 8.1.1
- 7.0.x -> 7.2.2.x -> 8.1.1
- 7.1.x-> 7.2.2.x ->8.1.1
As a generic rule, any release earlier than 6.0 would need to be upgraded to 6.3.6/7 first prior to upgrading
to 7.2.2 and then 8.1.1. Please consult the ASBCE upgrade guide for more information.
6.3 Upgrading the Hardware appliance

The ASBCE hardware appliances are not field upgradeable and therefore particular attention needs to be
paid during initial system engineering to ensure that the hardware ordered will fill the anticipated growth of
your customer network.
6.3.1 Upgrading from Hardware no longer supported in R8.1.1

Additional attention must be paid with any configuration including a CAD208 or R210 or R210-II hardware
appliance since these servers are no longer supported with Release 8.1.1 of ASBCE.

The following high-level steps are provided for Release 8 migration planning purposes are:
• Step 1 back up the appliance
• Step 2 upgrade the appliance to 7.2.2
• Step 3 back up the appliance again
• Step 4 Deploy and configure the new equivalent hardware to replace the one that is unsupported
with R8.
• Step 5 Restore the 7.2.2 backup
Refer to the upgrade guide (migration procedure section) for the detailed process.
In Release 8.1.1, the hardware equivalences from a capacity point of view are:
• Portwell CAD208 should be replaced by Portwell CAD230 for low end capacity appliance.
Alternatively, for capacity lower than 100 sessions, the cost-effective CAF 251 should also be
considered.
• R210 or R210-II should be replaced by Dell R330 or its upcoming successor the Dell R340 for mid-
range capacity appliance
6.3.2 Upgrading from CSR2 or CSR3 to ACP

Even if ASBCE Release 8 did introduce support for the newly launched range of ASP hardware, the release
8.x train continues to support the CSR2 and CSR3 based hardware appliances.
CSR2 based appliances are supported for upgrade only into R8.x (i.e. no new deployment)
CSR3 based appliances are supported for new (until stock lasts) and for upgrade into R8.x.
Two specific use cases are to be considered for a hardware appliance upgrade, hardware replacement (see
previous paragraph) or expansion
6.3.2.1System Expansion scenario

For the system expansion scenario, you can continue adding CSR3 based appliances as long they remain
available to your system (check End of sales announcements for any update) without any restriction.
You can also add any ASP based hardware to your existing CSR3 based system under one very specific
condition. ASP and CSR3 hardware cannot be mixed into the same High Availability (HA) pair. You can have
however CSR3 based HA pair(s) and ASP based HA pair(s) in the same ASBCE system (aka under the
same EMS) and therefore expand your system capacity that way.
6.4 Upgrade material codes and Pricing

6.4.1 ASBCE for Aura / Enterprise
The following table describes the material codes and associated pricing at the time of issuance of this
document for upgrade of 7.x to R8 basic licenses codes (standard, Advanced, and HA equivalent and
Dynamic).
Pricing are subject to change at Avaya’s sole discretion.

Standard Availability High Availability
LICENSES DESCRIPTION GLP LICENSES DESCRIPTION GLP
Standard
ASBCE R8 STD
ASBCE R8 STD
397193
SVCS UPG LIC
$ 22.00 397207 SVCS HA UPG $ 11.00
LIC

Dynamic Advanced
ASBCE R8 ADV
ASBCE R8 ADV
397200
SVCS UPG LIC
$ 16.00 397214 SVCS HA UPG $ 8.00
LIC

ASBCE R8
398047 DYNAMIC LICENSE $ 14.00 N/A N/A N/A
UPG
document for upgrade of R7.x to R8.x of system/a la carte license codes.
Note: New as of Release 8.1.1, Premium licensing has been introduced for enterprise – there is no upgrade
code since the functionality is new with Release 8.1.1

LICENSES DESCRIPTION GLP
ASBCE R8 SCOPIA
397223 VIDEO CONF UPG LIC $281
ASBCE R8 SCOPIA
397226 VIDEO HA UPG LIC $140
ASBCE R8 VE VAPP
397229 UPG LIC $0
ASBCE R8 ELEMENT
397218 MGR UPG LIC $0
397219 ASBCE R8 HA UPG LIC $0
ASBCE R8
397221 ENCRYPTION UPG LIC $0
6.4.2 ASBCE for MM/IPO

6.4.2.1Customers without IPOSS
document for upgrade of R7.x to R8.x basic licenses codes (standard, Advanced and HA).

DESCRIPTIO DESCRIPTIO
LICENSES GLP LICENSES GLP
Standard
N N
ASBCE R8
ASBCE R8
STD SVCS
397235 STD SVCS $ 15.00 397245
HA IPO UPG
$ 7.50
IPO UPG LIC
LIC
DESCRIPTIO DESCRIPTIO
LICENSES GLP LICENSES GLP
Advanced
N N
ASBCE R8
ASBCE R8
ADV SVCS
397240 ADV SVCS $ 6.00 397250
HA IPO UPG
$ 3.00
IPO UPG LIC
LIC
document for upgrade of R7.x to R8.x of system/a la carte license codes.
LICENSES
Material code DESCRIPTION GLP
397223 ASBCE R8 SCOPIA VIDEO CONF UPG LIC $281
397226 ASBCE R8 SCOPIA VIDEO HA UPG LIC $140
397229 ASBCE R8 VE VAPP UPG LIC $0
397218 ASBCE R8 ELEMENT MGR UPG LIC $0
397219 ASBCE R8 HA UPG LIC $0
397221 ASBCE R8 ENCRYPTION UPG LIC $0
6.4.2.2 Customers without IPOSS
As a generic rule, any release earlier than 6.0 would need to be upgraded to 6.3.6/7 first prior to upgrading to 7.2.2 and then
8.0. Please consult the ASBCE upgrade guide for more information.
The following table describes the material codes and associated pricing at the time of issuance of this document for upgrade
of R7.x to R8.x basic licenses codes (standard, Advanced and HA).
Please note the following process:

• Check and validate the IPOSS contract number and the Sold-to where the ASBCE licenses are present in PLDS.
• Check the ASBCE R7 codes for IPO and create the equivalent ASBCE R8.x codes for IPO in PLDS from the
mapping list below:

LICENSES
397236 ASBCE R8 STD SVCS IPO ENTL LIC $0
397241 ASBCE R8 ADV SVCS IPO ENTL LIC $0
397246 ASBCE R8 STD SVCS HA IPO ENTL LIC $0
397251 ASBCE R8 ADV SVCS HA IPO ENTL LIC $0
397254 ASBCE R8 SCOPIA VIDEO IPO ENTL LIC $0
397257 ASBCE R8 SCOPIAVIDEO HA PO ENTL LIC $0
397260 ASBCE R8 VE VAPP TRK CODE IPO UPG LIC $0
397262 ASBCE R8 ENCRYPTION FOR IPO UPG LIC $0
398198 ASBCE R8 SIG ONLY ENCRPT IPO UPG LIC $0
What if my IPOSS contract has lapsed? A re-initiation fee is required to reinstate IPOSS when coverage has lapsed. If
the customer is not on the most current release – a paid transactional upgrade to the most current release (including
both major and minor releases) is required. A re-initiation fee will not be applied to the upgrade. Refer to the IPO Support
Service Offer document and re-initiation fee policy:
https://sales.avaya.com/cs/Sites?lookuphost=/&lookuppage=/en/general/maintenance-support-reinitiation-fee-
policy
Note: as of the April 2019 version of A1S, IPO customers will be able to automatically process their upgrade into the
sales tool.
7 Product Specifications
7.1 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 and any other Avaya solutions.
Please visit https://secureservices.avaya.com/compatibility-matrix/menus/product.xhtml
7.1.1 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.
7.1.2 Avaya Endpoints
7.1.2.1Hardware Endpoints
Avaya J129 has been supported by ASBCE as of Release 7.2 .
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 3rd party SBC may change the port
post the initial handshake. If the 3rd 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)
7.1.2.2Software Endpoints
Like the prior version, ASBCE R8.1.1 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.1.1 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.
7.2 Interoperability with 3rd Parties
Due to its open implementation and rich feature set, ASBCE Release 8.1.1 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 3rd party and certified in some situations.
From a technical support point of view, while Avaya strongly recommends all third-party integrations and
vendors go through DevConnect Compliance Testing to ensure a higher level of comfort in the interoperability
between DevConnect member products and Avaya solutions, we recognize that is not always the case. If a
third-party product/integration is not tested under DevConnect, and a customer support ticket is raised to
Avaya services via an authorized Avaya support channel, Avaya will troubleshoot the issue to the Avaya
demarcation point with the third-party vendor to the best of our ability. If no issue is found on the Avaya side,
we will close the ticket and report to the customer that the issue needs to be worked with the third-party
vendor.

7.2.1 3rd parties Call Server
The following table shows tested interoperability for 3rd Party Call Servers
Call Server Release ( 3rd Party Call Servers ) ASBCE R8.1.1 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
SfB 2016 on premise Yes and certified by MSFT
MSFT Teams Yes and certified as of 08/04/2020 with SBCE 8.1.1
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 certification with Teams Direct Routing, please refer to SBCE documentation
“Working with MS teams” and Microsoft web site:
https://docs.microsoft.com/en-us/microsoftteams/direct-routing-landing-page
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 SfB 2015 compliance of ASBCE thru compliance with

prior Lync Version.
and
https://technet.microsoft.com/en-us/office/dn788945 capturing ASBCE compliance with Lync 2013.
Details and information regarding SFB2016 certification will be added to this offer definition document as they become
available post General Availability from Microsoft.
7.2.1 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
Details and information regarding SFB2016 certification will be added to this offer definition document as they
become available post General Availability from Microsoft
7.2.2 SIPconnect
Since Release 7.2, ASBCE is SIPconnect certified. For more information, visit SIP Forum.
7.2.3 3rd parties SIP endpoints
When used in combination with Avaya applications such as Oceana or Equinox or AEMO, ASBCE does not
support 3rd parties SIP endpoints unless validated by these Avaya offers or applications.

7.3 Solution capacities and Performance
ASBCE 8.1 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.
7.3.1 Solution capacities quick reference
7.3.1.1For new and current hardware:
Registered Single Internal External

Non- Encrypted or Scopia
Remote Worker SIPREC AAMS AAMS
Appliance Model Encrypted Premium Video Reverse Proxy
Users (Multi Transcoding Transcoding
Sessions Sessions Sessions
(Sessions) SIPREC) Sessions Sessions
500 HTTP Requests

/sec.
Avaya Converged Platform 10,000
20000 50 TLS connections
High Range
100 series server with 30,000 20,000 (See 800 1000 5000
(10,000) /sec
profile 5 Below)
2000 concurrent
WebSocket
Avaya Converged Platform 6,000
20,000
100 series server with 14,000 9,000 (See 800 1,000 2500 Same as above
(8,000)
profile 3 Below)
3,000
5,000
Dell R330/R340 6,000 4,000 (See 200 150 1,250 Same as above
(2,000)
Below)
2,500
Virtual Appliance 6,000
5,000 3,000 (See 200 100 1,250 Same as above
Mid-range
VMW/AWS/Azure (3,000)
Below)
2,500
Nutanix AHV on Nutanix 6,000
5,000 3,000 (See 200 100 1,250 Same as above
Appliance (3,000)
Below)
2,500
6,000
Aura Virtualisation Platform 5,000 3,000 (See 200 100 1,250 Same as above
(3,000)
Below)
Virtual Appliance
1500 500 500 N/A N/A 100 1,250 Same as above
KVM
Low Range
500
Portwell CAD0230 600 500 N/A N/A N/A N/A Same as above
(500)
Portwell CAF251 100 100 500(100) N/A N/A N/A N/A Same as above
SIPrec & Multi SIPrec Capacity Table
Single Rec Stream Two Rec Streams Three Rec Streams Four Rec Streams Five Rec Streams
Platform
Un- Encrypte Un- Encrypte Un- Encrypted Un- Encrypted Un- Encrypted
encrypted d encrypted d encrypted encrypted encrypted
ACP P5 15000 10000 10000 6666 7500 5000 6000 4000 5000 3333
ACP P3/G9
7000 4500 4666 3000 3500 2225 2800 1800 2333 1500
Hi cap
R340/R330/
G9 Mid cap 3000 2000 2000 1666 1500 1000 1200 800 1000 666
/Vapp

All of the capacity’s 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.
While implementing Remote Worker at maximum capacity limits, set registration expiry timers at Session
Manager and in every client at a minimum of 3,600 seconds or 1 hour.
While implementing Remote Worker at maximum capacity limits in one Avaya SBCE or HA pair, under worst
case failover conditions, re-registration for 10,000 users can take up to 20 minutes. During re-registration all
ongoing calls continue uninterrupted. However, under worst case conditions, a user cannot receive or make
new calls during this re-registration time period.
Distributing users across multiple Avaya SBCEs significantly reduces this re-registration time
The stated session capacities in high-end servers is achieved without Presence. For every 5000 users with
presence there is expected 10% reduction of supported concurrent sessions due to the high resource
utilization of presence traffic. For Mid-range and Low Range capacity is measured with Presence, having 25
contacts per user. Increased.
The capacity specifications mentioned above for ACP5 non-encrypted sessions are considering IPv4 as
transport and will have 20% reduction when IPv6 is required.
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.
• IPv4 as the transport protocol for calculating Non-encrypted Sessions with Trunking for Avaya
Converged Platform 100 series server with profile 5 (Dell™ PowerEdge™ R640 Server). With IPv6,
the value may decrease by 20%.
• All the Audio and Video session count are arrived assuming ASBCE anchors media.
• For all platforms (except CAD0230, CAF0251) the performance metrics are arrived by testing with
dedicated SBCE managed by separate EMS.

• Codec specification: The G729 and G711 Codecs are used for measuring transcoded capacities.
Different codecs will have varying results.
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; high-end hardware is measured with additional traffic of 50% of the maximum unencrypted
SIP Trunk Sessions
• 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
Note 4: The Multi destination SIPREC capacity are provided for two different destinations only at this stage
– Further information with 3 & 4 destinations will be published in this offer document once the data becomes
available.
Note 5 : The Multi SIPREC stream encrypted capacity in the multi SIPREC stream capacity table assumes
same crypto is used for all of the encrypted streams. If not then the capacity would be impacted – please
contact Avaya PLM for sizing/dimensioning in this situation.
7.3.1.2For legacy platforms supported as part of upgrades paths:
Registered
Encrypted Single
Non- Remote Scopia
or SIPREC Internal AAMS External AAMS Transcoding
Appliance Model Encrypted Worker Video Reve
Premium (Multi Transcoding Sessions Sessions
Sessions Users Sessions
Sessions SIPREC)
(Sessions)
500 HTTP
Requests /sec.
10,000
20,000 50 TLS
Dell R630 w/ Accelerator 30,000 9000 (See 800 1,000 5,000
(7,500) * connections /sec
Below)
2000 concurrent
webSockets
High Range
10,000
HP DL 360 G9 w/ 20,000
30,000 9000 (See 800 1,000 5,000 Same as above
Accelerator (7,500) *
Below)
6,000
20,000
Dell R630 Hi-Cap 14,000 9000 (See 800 1,000 2,500 Same as above
(7,500) *
Below)
6,000
20,000
HP DL 360 G9 Hi-Cap 14,000 9000 (See 800 1,000 2,500 Same as above
(7,500) *
Below)
3,000
4,000/ 5,000
HP DL 360 G9/G8 6,000 (See 200 300 1,250 Same as above
Mid-Range
2,000 (2,000)
Below)
3,000
5,000
Dell R320/R620 6,000 2,000 (See 200 300 1,250 Same as above
(2,000)
Below)

SIPrec & Multi SIPrec Capacity Table
Single Rec Stream Two Rec Streams Three Rec Streams Four Rec Streams Five Rec Streams
Platform
Un- Encrypte Un- Encrypte Un- Encrypted Un- Encrypted Un- Encrypted
encrypted d encrypted d encrypted encrypted encrypted
G9 Hi
7000 4500 4666 3000 3500 2225 2800 1800 2333 1500
cap/R630
G9 Mid
3000 2000 2000 1666 1500 1000 1200 800 1000 666
Cap/R330
All of the capacity’s 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.
While implementing Remote Worker at maximum capacity limits, set registration expiry timers at Session
Manager and in every client at a minimum of 3,600 seconds or 1 hour.
While implementing Remote Worker at maximum capacity limits in one Avaya SBCE or HA pair, under worst
case failover conditions, re-registration for 10,000 users can take up to 20 minutes. During re-registration all
ongoing calls continue uninterrupted. However, under worst case conditions, a user cannot receive or make
new calls during this re-registration time period.
Distributing users across multiple Avaya SBCEs significantly reduces this re-registration time
The stated session capacities in high-end servers is achieved without Presence. For every 5000 users with
presence there is expected 10% reduction of supported concurrent sessions due to the high resource
utilization of presence traffic. For Mid-range and Low Range capacity is measured with Presence, having 25
contacts per user. Increased.

• Codec specification: The G729 and G711 Codecs are used for measuring transcoded
• capacities. Different codecs will have varying results.
• IPv4 as the transport protocol for calculating Non-encrypted Sessions with Trunking for Avaya Converged
Platform 100 series server with profile 5 (Dell™ PowerEdge™ R640 Server). With IPv6, the value may
decrease by 20%.
• All the Audio and Video session count are arrived assuming ASBCE anchors media.
• For all platforms (except CAD0230, CAF0251) the performance metrics are arrived by testing with dedicated
SBCE managed by separate EMS.
7.4 Virtualization Resource Profiles

7.4.1 Summary Table for Resource Profile and capacity
The following OVAs are the only Virtual appliance footprint supported in R8.1.1 for the ASBCE. This is the
footprint whose capacities and performances are previously described.
Application Name vCPU CPU reservation Memory Hard disk Min Clock speed NICs
(MHz) (GB) (GB) (MHz)3
ASBCE Software 4 9600 8 160 2200 6
EMS Software 3 7200 8 160 2200 2
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.1, the OVA footprint can be adjusted ( see feature set for 8.1.1 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
7.5 Supported Hypervisors for Virtualized environment
ASBCE 8.1.1, like its predecessors, 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 7.2, and of course including all of the R8.x release train, 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 but cannot deployed in HW
mode in this environment for the time being.
7.5.1 VMWare vSphere
The following versions of VMware vSphere are supported with the ASBCE 8.1.1.
VMware ESXi ASBCE 8.0
VMware ESXi 5.0 No

VMware ESXi 5.1 No
VMware ESXi 5.5 No
VMware ESXi 6.0 √
VMware ESXi 6.5 √
VMware ESXi 6.7 √
VMware ESXI 7.0 Coming with SBCE 8.1.2
Note: ESXi 5.0, 5.1 and 5.5 are no longer supported by ASBCE starting 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.
7.5.2 KVM
Any KVM based on Linux kernel 3.10 and above is supported.
7.5.3 Nutanix AHV
ASBCE R8.1 was 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.
7.5.4 AWS
ASBCE R8 can be deployed on the current version of Amazon Web Service IaaS. As of Release
8.1.1, ASBCE can now be deployed in High Availability mode in AWS.
The HA failover performances are however different than on standard VE appliances.

If the connection between the Customer network and AWS cloud is VPN based then the HA failover
performances are in the range of 2-5s, meaning that during an SBCE HA failover the current active
calls will be maintained but the audio will be disrupted for 3s mean, 5s. worst case.
If the connection between the Customer network and AWS cloud is over the internet ( i.e. not VPN
based ) then the HA failover performances are in the range of 8-12s, meaning that during an SBCE
HA failover the current active calls will be maintained but the audio will be disrupted for 8s mean, -
12s. worst case. Even though our tests in lab have never demonstrated audio disruption for longer
than 8s, Amazon SLA indicates that the disruption could last up to 12s worst case.
7.5.5 Azure
New as of Release 8.1.1, SBCE can be deployed and run in Simplex mode only in Azure.
A new material code has been created which enables one to download the right packaging for
conversion into VHD and deployment in Azure environment.
7.6 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
7.7 Supported Hardware

7.7.1 Physical appliance
The ASBCE software is available as a bundle on its own set of hardware appliances as described in the
hardware section of this document.
The Dell, HP and Portwell platforms described in this document, are the only hardware platforms offered and
supported for ASBCE 8.1. No part substitution is allowed for those platforms.
7.7.2 Hardware support for Virtual Appliance

If the hardware is officially supported and certified by the supported hypervisors, it is supported by the ASBCE
Virtual Appliance OVA.

As a reference for ESXi, the list of certified hardware servers can be found at:
https://www.vmware.com/resources/compatibility/search.php
8 Product documentation
8.1 Release Notes
Release Notes are an asset when updating the system to the next release. This includes any bug fixes and
installation notes to make sure your update goes as smooth as possible. Release Notes are available at the
Avaya support center at http://support.avaya.com.
Also see Product Support Notices (PSNs).
8.2 User and System documentation
Product documentation is contained on the Avaya Sales Portal and the Avaya Support Portal.
• The Avaya Sales Portal (avaya.com=>partners=>mysalesforce.com=>products=>ASBCE)
o Product and Sales/SE Training, presentations, collateral
o Application Notes
• The Avaya Support Portal (avaya.com=>Support=>Support Portal=>products=>Avaya Session
Border Controller for Enterprise)
o Installing Avaya Session Border Controller for Enterprise
o Administering Avaya Session Border Controller for Enterprise
o Application Notes
The list of documents updated for ASBCE R8.1.1 is the following:
Title Support Site Link
Avaya Session Border Controller for Enterprise 8.1.1 https://support.avaya.com/css/P8/documents/101066431

PDF Library
Avaya Session Border Controller for Enterprise https://support.avaya.com/css/P8/documents/101063920
Overview and Specification
Deploying Avaya Session Border Controller for https://support.avaya.com/css/P8/documents/101063922
Enterprise on a Hardware Platform
Enterprise on a Virtualized Environment Platform

Enterprise on an Avaya Aura® Appliance
Virtualization Platform

Enterprise on an Amazon Web Services Platform

Enterprise on a Microsoft Azure Platform
Upgrading Avaya Session Border Controller for https://support.avaya.com/css/P8/documents/101063930

Enterprise
Administering Avaya Session Border Controller for https://support.avaya.com/css/P8/documents/101063932
Enterprise
Maintaining and Troubleshooting Avaya Session https://support.avaya.com/css/P8/documents/101063938
Border Controller for Enterprise
Working with Avaya Session Border Controller for https://support.avaya.com/css/P8/documents/101069910

Enterprise and Microsoft Teams
Enterprise Multi-Tenancy
Enterprise Geographic-Redundant Deployments
Avaya Session Border Controller for Enterprise https://downloads.avaya.com/css/P8/documents/TBD
Release Notes
Avaya Session Border Controller for Enterprise Port https://downloads.avaya.com/css/P8/documents/TBD
Matrix
Avaya Session Border Controller for Enterprise https://downloads.avaya.com/css/P8/documents/TBD
Privacy Statement
Avaya SBCE 8.1 Security Configuration and Best https://downloads.avaya.com/css/P8/documents/TBD
Practices Guide

9 Avaya Learning
9.1 Avaya Learning Center
Avaya’s primary training arm is Avaya Learning. Learning maps for various audiences are available from
Avaya Learning’s web site. https://www.avaya-learning.com The Avaya Learning website provides the
gateway to prepare you for the Avaya professional credentials.
Design Training
APDS-3170 - Avaya Enterprise Team Engagement Solutions – Please note this Credential curricula will retire 28 March
2020. Please refer to the new ACDS-3186 Avaya IX™ Calling Credential following the map below.
https://www.avaya-learning.com/lms/#/training/learning-maps/31
AAPDS-3170 - Avaya Enterprise Team Engagement Solutions

Learning
Course
Code Title Delivery Type Center
Duration
Deployment
Available Now
31200W Avaya Aura Solutions Overview 2 hours WBT
ASBCE Product Information Document (PID) linked to Available Now
n/a n/a PDF
31200W

Available Now
31500W Avaya Aura Solutions Customer Field Study 1 hour WBT
Available Now
3171T APDS Online Test 1.5 hours Online Test
ACDS-3186 - Avaya IX™ Calling Design

AACDS-3186 - Avaya IX CallingDesign

Learning
Course
Duration
Deployment
Available
31210W Avaya Aura® solution Overview for Design 2 hours WBT
Now
Available
31810W Designing the Avaya Aura® Solution Part 1 of 4 2 hours WBT
Now
Available
31820W Designing the Avaya Aura® Solution Part 2 of 4 2 hours WBT
Now
2 hours WBT Available
31830W Designing the Avaya Aura® Solution Part 3 of 4
Now
31840W Designing the Avaya Aura® Solution Part 4 of 4
Now
Available
31860X Avaya IX™ Calling Design Exam 2 hours Exam
Now

APDS-3770 - Avaya Midmarket Solutions – Please note this Credential curricula will retire 28 March 2020. Please refer to
the new ACDS-3781 Avaya Midsize Solution Design Credential following the map below.
APDS-3770 - Avaya Midmarket Solutions

Learning
Course
Duration
Deployment
Available Now
37200W Avaya Midmarket Solutions Overview 1.5 hours WBT
ASBCE Product Information Document (PID) linked to Available Now
n/a n/a PDF
37200W
Available Now
37400W Avaya Midmarket Solutions Customer Field Study 3 hours WBT
Available Now
3771T APDS Online Test 1.5 hours Online Test

ACDS-3781 – Avaya Midsize Solution Design Credential
AACDS-3787 - Avaya Midsize Solution Design

Learning
Course
Duration
Deployment
Available
37210W Avaya Midsize Solution Overview for Design 1.7 hour WBT
Now
Available
376810W Designing the Avaya Midsize Solution Part 1 of 4 2 hours WBT
Now
Available
37620W Designing the Avaya Midsize Solution Part 2 of 4 2 hours WBT
Now
37630W Designing the Avaya Midsize Solution Part 3 of 4
Now
37640W Designing the Avaya Midsize Solution Part 4 of 4
Now
Available
37820X Avaya Midsize Solution Design Exam 2 hours Exam
Now

Implementation and Support
ASBCE 8. requires ACSS certification to install and service the ASBCE product. The tables below list the
credentials and training that are relevant for Avaya Session Border Controller for Enterprise implementation
and support.
ACIS-7130 – Avaya Aura® Communications Applications
AACIS-7130 - Avaya Aura® Communications Applications

Course Learning Center
Code Title Delivery Type
Duration Deployment
Virtual Instructor Available

71300V Integrating Avaya Aura® Communication Applications 40 Hours
Led
Available
71300X Avaya Aura® Communication Applications Integration Exam 1.5 hours Exam

ACSS-7230 – Avaya Aura® Communications Applications
AACSS-7230 - Avaya Aura® Communications Applications

Duration Deployment
Avaya GSS Troubleshooting and Engagement Available Now
72220W 2 Hours WBT
Methodology
Virtual Instructor Available
72300V Supporting Avaya Aura® Communication Applications 40 Hours
Led Now
Available
72300X Avaya Aura® Communication Applications Support Exam 1.5 hours Exam
Now
ASTA-9110 – Avaya Session Border Controller for Midmarket Solutions

AASTA-9110 - Avaya Session Border Controller for Midmarket Solutions
Duration Deployment
Avaya Session Border Controller for Midmarket Solutions Available
70080W 5 hours WBT
Implementation and Support Now
Avaya Session Border Controller for Midmarket Solutions Available
70080T 1.5 hours Online Test
Implementation and Support Test Now
ASTA-9140 – Avaya Session Border Controller for Enterprise Platform Independent

AASTA-9140 - Avaya Session Border Controller for Enterprise Platform Independent
Duration Deployment
Implementing and Supporting Avaya Session Border Virtual Instructor Available
20800V 24 hours
Controller - Platform Independent Led Now
Avaya Session Border Controller for Enterprise Platform Available
20800T 1.5 hours Online Test
Independent Implementation and Support Test Now
Administration
Additionally, the Avaya Solutions Administrator and Developer Certificate Program designed for Avaya
customers and Partner community, offers two distinct curriculum paths for the roles of “Administrator” and
Developer/Programmer”. This global program offers candidates the opportunity to acquire the necessary
competency skills essential for successfully performing administrator or developer job functions when
managing an Avaya product solution and applications. A Certificate is available to be earned for Avaya
Session Border Controller for Enterprise Administration.
ASAC-0023 – Avaya Session Border Controller Administration

ALS-0022 - Avaya Session Border Controller Administration
Learning
Course
Duration
Deployment
Administering the Avaya Session Border Controller for Available
20660W 6 hours WBT Mar 2019
Enterprise
Administering Avaya Session Border Controller R7 Available
20660T 1.25 hours Online Test Mar 2019
Online Test

10 Product Ordering, Licensing and Pricing
The product structure, part codes, etc., are constructed as follows.
• One Software product: ASBCE 8.1.1 continues as a single software product, the one software
product supports both large enterprise and SME. The 8.1.1 Media kits available just after GA will
only incorporate release 8.1.1 software and include a USB and a DVD kit.
• Software Licensing: The Standard and Advanced services licenses continue forward for Avaya
ASBCE 8.1.1 as well as the license for Scopia Video service that supports Scopia video conferencing
needs for users of the Scopia SIP clients as Remote Workers. A new Premium Tier of license is
however introduced as of Release 8.1.1 and enables Microsoft Teams Direct Routing integration
• Hardware Configurations: Hi-Cap servers, the HP DL360 G9 and the Dell R630, with and without
accelerator card will remain available at the early stage of the release but will be gradually replaced
by ASP profile 3 and ASP profile 5; Mid-Range servers, the HP DL360 G9 is no longer available for
new sales with R8.1 and for mid-size appliance, the Dell R330 will be gradually replaced by the Dell
R340 as R330 stock depletes; and Portwell small server, the CAD-0230 & CAF-251.
Avaya’s pricing strategy for ASBCE release 8 has been simplified; the volume tiering structure previously
available with earlier releases has been discontinued starting with Release 8.0.
The Standard, Advanced licenses and their HA variants licenses for both Aura and IPO segments are now
only available without volume tiering. Their respective pricing has been adjusted accordingly starting in
February 11th 2019.
Like for prior version of the software, the pricing for the ASBCE is based on per-session software licensing
plus add-in in the hardware platforms that support the software and allow for scale. Standard Services
licenses include everything that is required for SIP trunking implementations. Advanced Services are
‘additive’ on top of Standard Services and deliver Remote Worker, Encryption and Media Forking capabilities.
Newly introduced with Release 8.1.1, the Premium tier of license , additive on top of Standard services and
Advanced, has been created to deliver premium type of feature such as Microsoft Teams Direct routing
integration and like Stnadard and Advnaced, has an HA equivalent and is required on a per session basis.
Support Advantage services are the Maintenance services available for the Enterprise/Aura customers of
ASBCE 8.0. Software maintenance services is offered with only Preferred support options (1-Yr, 3Yr and 5-
Yr annual billing and Pre-Paid). Upgrade Advantage is also a required attach as of R7. Hardware Advantage
services are also available.
The IP Office Support Services (IPOSS) offers (1-Yr, 3Yr and 5-Yr Pre-Paid) codes are based on the current
IPOSS offer used for IP Office. This offer leverages the same codes and coverage, and do not require re-
entry to Partner databases. The codes are provided for reference in a next chapter of this section.
10.1 Quoting and Ordering Tools/Procedures
The Enterprise/Aura offer for ASBCE 8.1.1 is quoted via One Source with the Avaya Solution Designer (ASD)
quoting and ordering tool

The SME/IP Office offer is also configured primarily in One Source for IP Office 9.x.
Any pricing contained within, while accurate at the time of publication, should be considered as unofficial; the
reader is directed to verify the accuracy of all prices cited. The pricing in this document is based on Global
List Pricing in US dollars. For regional list prices please refer to your local price list and associated ordering
tools for complete information.
10.1.1 ASBCE in A1S
ASBCE in ASD is designed within the Communication Manager (CM) configurator on the Session Manager
page to ease ordering of the end-to-end Aura SIP core. Continuing for release 8.1.1 is the ability to configure
multiple ASBCE instances for one CM ‘system’. This is accomplished by moving the configuration screen for
ASBCE to the Location level. (Location > Hardware/Software > ASBCE screen).
Starting from Release 8.1, A1S offers the ability to configure and dimension a system with the SIPREC
feature – A1S will continue evolving to add Multi destination SIPREC configurability over the next several
iterations. Customers and partners requiring system sizing /engineering design should contact ATAC for
assistance.
New as of Release 8.1.1 and in A1S August 3rd 2020 release, Avaya Sales and Partners can leverage the
quote tool to size and price any SBCE configuration requiring Microsoft Teams integration.
The A1S user answers the same simple questions in the tool to configure as for prior ASBCE releases, but
must now answer them per location for each required ASBCE 8 (same since release 7.1)
• As part of a new Aura/CM system, ASBCE 8 can be added to the configuration.
• The A1S user must take care to properly calculate the numbers of Standard Services sessions, the
number of Advanced Services sessions, the number of CES-supporting sessions and the number of
Video (Scopia Video SIP clients supported as Remote Workers) needed for the implementation.
• A1S platform choices are chosen based on customer needs for the solution. For example, a system
defined as needing 105 Standard Services sessions for secure SIP trunking could select the Portwell
CAD-0230 platform as a choice. The ASD user can use the drop-down box to select the Dell, HP
(while it lasts), ASP or Virtualization as a platform if desired.
o The ASD implementation for ASBCE 8 looks and calculates an ASBCE system for the
network location (Location level) and assumes a single system per location. Multiple
locations can be provisioned.
o Platform choices are driven by the capacity table included in this document
o The HA choice delivers the Dell, HP (while it lasts), ASP 110, ASP 120 (AVP) or
Virtualization platform alternatives, the Portwell platform does not support HA. The HA
choice drives the 3-server configuration and the extra licensing for the HA configuration and
separate EMS server
o If Encryption is being used, a system level encryption will be added (to differentiate for the
export restrictions for encryption) but will drive Advanced Services licenses since an
encrypted session (whether trunk or RW) will consume an Advanced license.
• Support Advantage (SA) is a mandatory attach for all Enterprise/Aura implementations of Avaya
ASBCE 8.. Support Advantage leverages the Maintenance configurator of A1S. ASBCE

Maintenance services will be aligned to the SA options chosen for the other elements of the Aura
core, there cannot be differing support arrangements for different parts of the solution.
10.1.2 ASBCE 8.1.1 with IP Office 11.x (or above)
The offer for ASBCE 8.1.1 with IP Office 11.x is quotable via Avaya One Source (A1S) in the IP Office
Configurator to align with ordering of the IP Office 11.x. and 10.x solutions. This significantly simplifies quoting
and ordering for the IP Office Distributor partner and Business partner when an ASBCE solution for IP Office
10.x (or above) is required.
The offer mechanics in A1S (specifically for the IP Office implementations) are simple
• The customer orders either an ‘all SIP trunking’ option, or orders SIP trunk licenses for their IPO to
use SIP trunking
• The tool the ‘pops’ an extension to the menu that shows the ASBCE 8.1.1 as ‘selected’, with an
option to manually de-select the ASBCE. The second part of this menu extension allows inputting a
desired number of ASBCE Advanced Services sessions with IP Office 11.x.
• If the customer chooses an IPOSS offer for the IP Office 11.x solution, the associated IPOSS offer
for the ASBCE 8.1 is also quoted
o Quoting of the IPOSS for ASBCE reflects either the Portwell or Dell R330 or Dell R340 and,
if HA, three-server configurations for the R330/R340 HA pair + the EMS R330/R340 server
(Portwell does not support any HA option)
o The IPOSS quote output will show the added server (s)
Orders for IP Office solutions by Business Partners for end customers are all placed with Distribution
Partners. Distribution Partners facilitate the product ordering process for Business Partners and use EDI tools
for ordering to Avaya for the solution. Distributor Partners often have their own ‘home-grown’ tools for quoting
purposes and can also use Avaya tools.
It is noted here that ACSS certification on the ASBCE product is required to perform installation and service
for the product. Avaya Professional Services (APS) can perform the ASBCE 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 ASBCE product itself, it is assumed the
Business Partner is certified to perform all services for either the Aura core or the IP Office or will order those
appropriately from APS as needed.
10.2 Buy to Current
Effective 14-Nov-2016, Avaya implemented a new ordering process for products that offer overlapping
Software Releases: Release N (e.g. R8 as of February 11th, 2019) and Release N-1 (e.g. R7. Buy to Current
requires customers to always purchase the most current software release offer, including upgrade advantage
and support advantage for the future, and still enable the deployment of the N-1 release as their business
needs dictate.
This is a process change, not a promotion or program. It applies to all future enterprise products that offer

overlapping Release N and Release N-1.
This process does NOT change the normal software release lifecycle planning. When an N-1 release is made
end of sale (EOS), the tools will be updated and only offer the N release for deployment. Systems ordered
or deployed prior to 14-Nov-2016, will continue to allow additions/expansions in their current deployed release
offer until the N-1 Add/Expansions are made End of Sale (availability).
Avaya Aura Suite Licensing, Session Manager, System Manager, AES and ASBCE are initial products that
leverage the Buy to Current Process.
Read the Buy to Current offer definition here: https://sales.avaya.com/documents/1399624278972
10.3 Suite Licensing with Avaya Aura
Avaya Aura Suite Licensing is offered as 2 licensing packages (Core and Power Suites). The Core Suite
combines the elements of the Foundation Suite with mobility applications. The Power Suite is all of the
elements of the Core Suite with enhanced Messaging applications and Avaya Aura Conferencing.
ASBCE 8.x is integrated into the new Core and Power Suites by incorporating licensing support for one
Remote Worker session and one SIP trunking session, in HA format, for every seven (7) Core or Power Suite
named user.
• The Remote Worker entitlement: (1 x Advanced SA + 1 x Advanced HA + 1 Standard SA + 1 x
Standard HA) session licenses for every 7 Core or Power Suite users
• The SIP trunking entitlement: (1 Standard SA + 1 x Standard HA) session licenses for every 7 Core
or Power Suite users
The user will buy all required hardware and any extra licensing required a la carte. Engineering rules in
section below, define the calculations for required session licensing.
Note : Dynamic licenses and Premium licenses are not offered and included as part of the suite licenses.
These licenses are only available a la carte or via the subscription model.
10.4 Product Order Codes, structure and Pricing
The software functionality of ASBCE 8.1.1 continues with feature license groups: Standard and Advanced
services, Scopia Video license, CES license, dynamic license and signaling only encryption license for
Russia, Belarus and Kazakhstan, but it also introduces a new Premium tier license on top of Standard and
Advanced.
10.4.1 License Structure

The ASBCE is extremely rich in term of functionalities and offers several tiers of features 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 special licenses,
do not follow this incremental behavior. (see license descriptions in the following chapters)
Note: 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 in this section 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 e then a standard license AND an advanced license will need to
be ordered.
Similarly, the Premium will require a Standard license AND an advanced license underneath to become
operational.
And finally, 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, advanced licenses and Premium
licenses associated with the appliance.
The following diagram represent the incremental structure of Standard, Advanced, Premium and High
availability licenses
To further describe this, the following examples illustrate what has been described above:
Example 1:
A customer is purchasing an ASBCE for which it requires support for up to 500 SIP trunks and 1000
Remote users. The licensing required would then be 500 Standard for the SIP trunks, plus 1000
Standard AND 1000 advanced for the Remote users feature for a total of 1500 standard licenses and

1000 advanced licenses.
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 1500 High Availability standard licenses to cover
the 1500 standard licenses and 1000 Advanced HA to cover the advanced licenses.
10.4.1.1 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/Blacklisting
• 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
10.4.1.2 Advanced License
Advanced services deliver unique features that work in addition to the Standard Services functionalities.
Access to any of the following features will require an Advanced service license:
• Remote Worker – 1 session
• Encryption service- 1 session
o SIP TLS
o SRTP
• Media Replication

o Media forking to recording devices – SIPREC
o UCID generation
• SIP OneX Agent support (for CCaaS only)
• STUN/TURN functionality for WebRTC support.
• Reverse Proxy
The advanced license consumption is incremental when the service consumed is within the same category.
As an example, 3 remote workers all 3 with encryption and all 3 being recorded using SIPREC will only require 3 advanced
licenses (on top of the 3 standards needed for the 3 sessions).
On the other hand, a system offering 20 SIP trunks with no encryption, 10 of these trunks recorded and 2 remote workers
which are not contact center agents and not using any of the recorded trunks, will require 22 standards and 12 advanced.
A variance has been introduced in Release 8.1 regarding the behavior of the advanced license to deal with the special case
of multi destination SIPREC.
For a single destination SIPREC, the licensing behavior is unchanged and identical to the behavior pre R8.1, ie if 1 SIP trunk
call needs to be recorded using SIPREC then 1 standard ( for the trunk session ) and 1 advanced ( for the SIPREC) needs
to be added to the system. If the SIP trunk happens to be encrypted, then the standard + advanced licenses needed for the
encrypted call will also include the single destination SIPREC.
However, with the introduction with Multi destination SIPREC, an additional Advanced license (but no additional standard
required) will be required for each additional destination on top of the first one.
For a SIP trunk call which is being SIPREC’ed to 3 destinations will require 1 standard + 1 advanced for the SIP trunk call +
first SIPREC session AND (this is the new licensing behavior) 2 additional advanced for a total of 1 standard and 3
advanced.
The same behavior will apply for encrypted SIP trunk where the 1 standard +1 advanced required for the encrypted call will
open up the first SIPREC session as well, but 2 additional advanced will be required to open up the two additional SIPREC
destination for this SIP trunk call.
10.4.1.3 Premium License
A new tier of licensing, Premium, has been introduced as of ASBCE Release 8.1.1. This new tier of licensing is additive to
Standard and Advanced, the same way Advanced is to Standard (refer to section 10.4.1 for more details).
Like for Standard or Advanced, the Premium license is sold and sized on a per session basis. ( 1 session =1 license unit
required )
This Premium tier of licensing is reserved for the highest value features and control access to the following functions in
SBCE 8.1.1:
• Microsoft Direct Routing – 1 session
10.4.1.4 High Availability License
A High Availability license is required for each standard license or advanced license or premium license in
one given appliance to enable proper licensing for a High Availability pair.

10.4.1.5 Dynamic License
Introduced since 7.2.0, Dynamic Licensing enables other licenses to 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, Premium,
Transcoding, Scopia) all become dynamic and follow the pooling behavior.
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
These are configured in the EMS GUI.
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 (if 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.
Please note ASBCE will not block any traffic if it fails to acquire license for the session but generates an
incident notification (Alarm message in log).
The following several slides describes the difference in system behavior between static licensing and
dynamic licensing.
In static mode:

In Dynamic mode:
Note : the diagrams above do not represent an example of Premium tier – the dynamic licensing behavior is
exactly the same regardless.
10.4.1.6 Additional License (“special” 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 a feature activation and are per session.
10.4.1.6.1 Client Enablement Service (CES) inspection License
This license continues for release 8.1 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 either on iOS or Android) 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.
10.4.1.6.2 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)
10.4.1.6.3 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 the proper type of encryption when required.
This is a zero-dollar license.
10.4.1.6.4 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
10.4.1.6.5 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 1: 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.
10.4.1.6.6 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.
10.4.1.6.7 KVM deployment license
Introduced since 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)
10.4.1.6.8 AWS deployment license
Introduced since 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.
10.4.1.6.9 AZURE deployment license
New with ASBCE release 8.1.1, this is a per appliance license granting its owner the right to deploy one

instance of the Virtual appliance in Microsoft Azure environment.
10.4.2 Product Codes and Pricing
Besides Product codes and associated pricing, there are slight variations in the availability of the ASBCE
offer for the enterprise segment and Mid-Market/IPO.
The following two sections highlight these differences
10.4.2.1 Avaya ASBCE and Aura/Enterprise
The product structure, part codes, etc., are constructed as follows.

• One Software product – ASBCE 8.1.1 continues as a single software product, the one software
product supports both large enterprise and SME. The 8.x Media kits available just after GA will
incorporate release 8.1.1 software and include a USB and a DVD kit.
• Software Licensing – The Standard and Advanced services licenses continue forward for Avaya
ASBCE 8.1.1 as well as the license for Scopia Video service that supports Scopia video conferencing
needs for users of the Scopia SIP clients as Remote Workers. A new Tier of license, Premium is now
being introduced in Release 8.1.1 to capture and control the usage of the high value features such
as Microsoft Direct Routing sessions.
• Hardware Configurations – Hi-Cap servers, the HP DL360 G9 and the Dell R630, with and without
accelerator card while stock last, ASP Profile 3 and ASP Profile 5; Mid-Range servers, the Dell R330
for mid-range; and Portwell small servers, the CAD-0230 and CAF-0251.
The high-level structure is illustrated below:
ACP P3 & P5
R340
CAF 251
CAF 251
As seen in the diagram, Avaya Session Border Controller for Enterprise 8.1.1 continues as a single software
product that can serve many applications needs for SIP-based communications in the Enterprise. The
software is delivered, with our Business Partners in mind, pre-loaded on the hardware platforms, on DVD or

on a Thumb Drive for physical media (platform dependent), and, aligning with other Avaya applications, via
PLDS.
The software functionality of ASBCE 8.1 continues with feature license groups Standard , Advanced services,
Scopia Video license, CES license , dynamic license and adds Premium licensing as of release 8.1.1.
• Standard Services
• Advanced Services
• Premium Services
• CES
• Transcoding
• Scopia Video
• Dynamic
• Encryption
• Signaling Only
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.1.1. 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.1 is specifically required for Portwell platforms and can be used for the newer
platforms also.
Pricing shown is subject to change at Avaya sole discretion.
ASBCE Rls 7.x Media Kits
700514240 ASBCE R8.x SYS SFTW USB - $ 50.00
700514239 ASBCE R8.x SYS SFTW DVD $ 50.00

ASBCE R8.x
SYS SFTW
Material codes for Media
DVD Kits are the same for Enterprise and Mid-Market/SME.

The following table capture the different license material codes making up the basic incremental licensing structure of the
ASBCE, with their description and Pricing at the time of the issuance of this document.
These are per sessions licenses
Pricing is subject to change at Avaya sole description.

Standard
LICENSES LICENSES
DESCRIPTION GLP DESCRIPTION GLP
Material code Material code
ASBCE R8 STD ASBCE R8 STD

397188
SVCS LIC $65.00 397202
SVCS HA LIC $32.00
LICENSES LICENSES
Advanced
ASBCE R8 ADV SVC ASBCE R8 ADV

397195
LIC $45.00 397209
SVCS HA LIC $22.00
LICENSES LICENSES
Premium
ASBCE R8 ASBCE R8
406671 PREMIUM SVCS $30.00 406672 PREMIUM SVCS $15.00
SESS LIC SESS HA LIC
LICENSES LICENSES
Dynamic
ASBCE R8 DYNAMIC
398042
LICENSE $50.00 N/A
The following table describes the a la carte licenses material codes available and associated pricing at the
time of issuance of this document. Pricing subject at Avaya’s sole discretion.
These are also per session licenses
LICENSES LICENSES
ASBCE R8
397265 ASBCE R8 CES LICENSE $15 397267 TRANSCODING SES $75
LIC
ASBCE R8
397266 ASBCE R8 CES HA LICENSE $8 397268 TRANSCODING SES $38
HA LIC
ASBCE R7 SCOPIA VIDEO ASBCE R7 SCOPIA

397222 CONF LIC
$850 397225 VIDEO HA LIC
$425

The following are per appliance (Encryption and HA) or per system (EMS) licenses
LICENSES LICENSES Material

Material code code
ASBCE R8 ELEMENT MGR

397216 LIC
$0 397217 ASBCE R8 HA LIC $0
ASBCE R8
ASBCE R8 ENCRYPTION
397220 $0 397270 SIGNAL ONLY $0
LIC
ENCRYPTION
Note: The Virtual appliance licenses are captured and described in the virtual appliance description
section of this document and can be found here
10.4.2.2 Avaya ASBCE and IP Office
Avaya ASBCE 8.1.1 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.1.1 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.1.1 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.
The structure of the offer for IP Office is shown below:
R340
CAF 251
Note: R330 model will ship while stock lasts, after which the Dell R340 will remain the only hardware

appliance shipping for Mid-range offer for SME segment
Aligned and essentially like Enterprise, Avaya Session Border Controller for Enterprise 8.1.1 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, pre- loaded 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.1.1 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.1.1 is specifically required for Portwell platforms and can be used for
the newer platforms also.
Pricing shown is subject to change at Avaya sole discretion.
ASBCE Rls 7.x Media Kits
700514240 ASBCE R8.X SYS SFTW USB $50
700514239 ASBCE R8.X SYS SFTW DVD $50
Material codes for Media Kits are the same for Enterprise and Mid-Market/SME.
The following table capture the different license material codes making up the basic incremental licensing
structure of the ASBCE, with their description and Pricing at the time of the issuance of this document.
Dynamic licensing for Mid-Market was introduced as of SBCE Release 8.1

licenses Description GLP Licenses Description GLP
Standard
397232 ASBCE R8 STD SVCS IPO LIC $55.00 397242 ASBCE R8 STD SVCS HA IPO LIC $27.00

Advanced
397237 ASBCE R8 ADV SVCS IPO LIC $30.00 397247 ASBCE R8 ADV SVCS HA IPO LIC $15.00

Dynamic
404120 ASBCE R8 DYNAMIC LICENSE IPO $50.00 N/A N/A N/A
The following table describes the a la carte licenses material codes available and associated pricing at the
time of issuance of this document. Pricing subject at Avaya’s sole discretion.

Note: as of Release 8.1.1, Premium licensing has not been made available for Mid-Market
These are per session licenses
LICENSES Material code DESCRIPTION GLP

ASBCE R8 SCOPIA VIDEO
397252 $850
CONF IPO LIC
ASBCE R8 SCOPIA VIDEO
397255 $425
HA IPO LIC

The following are per appliance or per system licenses
LICENSES Material code DESCRIPTION GLP

ASBCE R8 ELEMENT
397216 $0
MGR LIC
397217 ASBCE R8 HA LIC $0
ASBCE R8 ENCRYPTION
397261 $0
FOR IPO LIC
ASBCE R8 SIGNAL ONLY
397271 ENCRYPTION FOR IPO $0
LIC
10.4.3 Virtual Appliance Order codes and Pricing
ASBCE 8.1 can be deployed as a virtual machine within a VMware, AVP, 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 sections list the different virtual appliances licenses related to the type of environment you/your
customer are/is considering deploying into
10.4.3.1 VMW & AVP Order codes and Pricing
For Aura/enterprise
LICENSES
DESCRIPTION GLP
Material code
ASBCE R8 VE VAPP
397228 $400
FILES LIC
For IPO/Mid-Market – VMW only ( AVP not available for IPO/Mid-Market)

LICENSES
DESCRIPTION GLP
Material code
ASBCE R8 VE VAPP
397258 400
IPO FILES LIC

10.4.3.2 AWS Order codes and Pricing
For Aura/Enterprise
LICENSES
DESCRIPTION GLP
Material code
ASBCE R8 AWS
398475 $400
AMI ENABLE LIC
For IPO/Mid-Market
LICENSES
ASBCE R8 AWS AMI
398472 400
ENABLE IPO LIC
10.4.3.3 KVM Order codes and Pricing
This is also covering a Nutanix AHV deployment
For Aura/Enterprise
LICENSES
DESCRIPTION GLP
Material code
ASBCE R8 KVM
398474 $400
ENABLE LIC
For IPO/Mid-Market
LICENSES
ASBCE R8 KVM
398473 400
ENABLE IPO LIC
10.4.4 Azure order Codes and Pricing
For Aura /Enterprise
LICENSES
DESCRIPTION GLP
Material code
ASBCE R8 AZURE
407607 $400
ENABLE LIC
For IPO/Mid-Market
As of Release 8.1.1, the Azure simplex deployment is only offered against
Aura/Enterprise platform

10.4.5 Hardware Appliances Order codes and Pricing
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.1.1 hardware materials required for supporting the product can be ordered separately by
Distributor Partners, or, in configurations generated by the configuration tools
10.4.5.1 ASBCE for Enterprise
Release 8.1 continues to support the ASP based appliance as an alternative of the HI CAP with Accelerator
with the ASP P5 ASBCE, an alternative for the Hi CAP with the ASP P3 ASBCE and a new low-end appliance
from Portwell, the CAF-251. In addition, Release 8.1 also introduces support for the R340, the new mid-size
hardware appliance which will replaces the R330 once the stock has depleted.
All of these appliances are identified in bold in the table below.
Pricing shown is subject to change.

ASBCE Enterprise Hardware Codes
Part Codes DESCRIPTION PRICE
388046 R630 HI CAP INT ACC SRVR ASBCE* $48,500.00
388047 DL360 G9 HI CAP INT ACC SRVR ASBCE* $48,500.00
700514265 ASP 110 DELL SRVR P5 ASBCE $24,500.00
381667 R630 HI CAP SRVR ASBCE $25,000.00
381668 DL360 G9 HI CAP SRVR ASBCE* $25,000.00
700514264 ASP 110 DELL SRVR P3 ASBCE $12,300.00

388048 R330 MID RANGE SRVR ASBCE* $8,700.00
700515007 ASP110 DELL R340 MIDRANGE SRVR ASBCE $4,800.00
388052 ASBCE CORE PORTWELL CAD-0230 $1,950.00
700514948 ASBCE PORTWELL CAF-0251 $1,100.00
*: While supplies last
Portwell Power Supply can be ordered separately (700513204)
10.4.5.2 IPO/Mid-Market
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 PRICE

388053 ASBCE CORE PORTWELL CAD-0230 IPO $ 1,950.00
700514948 ASBCE PORTWELL CAD-0251 IPO $ 1,100.00
388049 R330 MID RANGE SRVR IPO ASBCE $ 8,700.00
700515008 ASP110DELL R340 MIDRNG SRVR IPOASBCE $ 4,800.00
Portwell Power Supply can be ordered separately (700513204)
10.4.6 Product Bundling
Avaya order codes for software licensing are indicated in the previous sections. Ordering the software license
generates an entitlement that is downloadable as a file from PLDS and loaded into WebLM during installation.
The hardware platforms are pre-loaded with ASBCE software. The codes are ‘bundle’ codes that indicate a
box containing
• The supported Dell, HP and Portwell servers will be pre-loaded with ASBCE 8.1.1 software from
August 4th, 2020 for new system sales
• All ASP and the Dell R330/R340 come from the factory with Dual Power supplies. Make sure
appropriate power cords for the ship-to country are ordered
• Rails for 19” rack mounting or an ‘L’ shaped mounting bracket for rack mount (in Portwell case, unit
can be desktop or rack)
• Part code 700514240 USB thumb drive or 700514239 DVD containing a copy of ASBCE 8.1.1 for
Service/support issues
• Associated documentation for EULA, Warranty, etc.
11 System Engineering Consideration

11.1 Prerequisites
ASBCE release 8.1.1 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.
• SAL Gateway is assumed to be in place for remote access in an Enterprise implementation with
Aura.
• SSL VPN connectivity and registration is assumed for IP Office implementation.

11.2 Network Rules
This offer of ASBCE 8.1.1 delivers Standard, Advanced, CES, Transcoding and Scopia Video features for
the Enterprise/Aura customer, and Standard and Advanced service for the SME/IP Office customer. At a high
level, following is the Sales Engineer’s required ‘thinking’ steps for ASBCE 8.1.1:
• 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 feature and the Advanced Services feature
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.x 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
o Note: In the absence of a mixed-use dimensioning tool, Engagement with ATAC for such
complex dimensioning is highly recommended
• CES licensing, introduced in ASBCE 7.0, serves a unique security enhancement for Remote Workers
using the Avaya Communicator and Avaya Equinox family of mobile clients. Calculate license
requirements as the sub-set of sessions serving Remote Workers using the Avaya Communicator
or Avaya Equinox mobile clients.
• The Transcoding license was added starting in ASBCE 7.1. This initial function supports transcoding
for a subset of the trunk traffic coming into the network. Support would be for specific needs driven
by, say, a 3rd Party application that can’t auto-negotiate to the normal CODEC offered by the SIP
trunk provider (generally G.729).

The note above to ‘Know your traffic requirements’ is a key to successfully deploying ASBCE 8.1.1. Some
examples of calculating session and licensing requirements follow:
Example 1: A customer is implementing SIP trunking to replace TDM trunking for a location with 1500
general population users. Using the general ‘rule of thumb’ of a 5:1 user to trunk ratio, 300
simultaneous sessions are required. This requires 300 Standard Services licenses and the choice of
Dell or HP platforms (the Portwell, as it can serve up to 500 Standard Service sessions, could be
technically used, but the customer is likely to want HA). The choice of platform can be driven by
customer desire. Usually the customer will want HA for production, so Dell and HP become the
appropriate choices.
Example 2: A customer desires to serve a population of 500 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 167-200
Advanced Services licenses and 167-200 Standard Services licenses (as every Advanced Service
license requires a Standard Service license). Also remember that using Encryption Service (part of
the Advanced Service license) reduces the capacity of the hardware, per the table in section 5.2). The
Portwell server could be used; the Dell or HP server might be recommended if the customer is thinking
about HA or expansion in the future.
Example 3: A site with 2500 users, containing a sub-population of 250 Remote Workers wants to
implement a mixed-use ASBCE 8.1. For the general population of 2250, 450 Standard Services
sessions are required at the 5:1 ‘rule of thumb’. For the 250 Remote Workers, the requirement is 100
Advanced Service licenses + 100 Standard Service licenses (as every Advanced Service license
requires a Standard Service license). The system totals are 550 Standard Service licenses and 100
Advanced Service licenses. As we are running Remote Worker in the appliance, Encryption services
are invoked, and the required total simultaneous sessions for this system are 550. A Dell or HP
configuration is required as maximum total sessions for the Portwell platform is 500 when encryption
is invoked.
Example 4: A customer wants to use an ASBCE 8.1 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.1, 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 will handle the traffic within one system.
These provisioning considerations and engineering rules apply to both the Enterprise and the Mid-market for
IPO 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.

11.3 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.1.1 cannot work when in parallel to the Enterprise firewall, but,
security best practices promote a layered defense strategy, hence the recommendation that ASBCE 8.1.1
be locate behind the enterprise firewall.
The following topology illustrates the best practices deployment for enterprise and SMB respectively
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.1.1
should consider the following:
• IP networking for the ASBCE
• Remote access to the system via SAL (for the Enterprise/Aura) or 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.1.1 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.1.1 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.1.1 is attached to that one
site. If SIP trunks are provisioned at multiple sites, then an ASBCE 8.1.1 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.
11.4 Configuration Tool and Misc. Engineering Tips

11.4.1 Configuration Tool
The Avaya One Source tool is the primary Quotation and Ordering tool for Enterprise/Aura implementations
of Avaya ASBCE 8.1. We are evolving the tool capabilities regularly.
A new configurator for ATAC and Avaya internal Sales Engineering usage has been created and is
maintained by ASBCE engineering to enable sizing simulation of multi SBCE multi location configuration
computation with simultaneous feature usage requirements. This tool is not a replacement for A1S as the
tool does not have pricing information or ordering processing ability but is a great assistance to design an
understand the elements/quantities needing to be ordered in support of complex SBCE configurations.
The SBCE engineering configurator can be found at (requires Avaya intranet/VPN connection):
https://configurator.sbclabs.avaya.com/
Note: This is an internal tool running on an internal server with no guaranteed SLA provided on a best
effort basis - The URL provided above could go down for maintenance or upgrade at any time w/o
prior notice, and for an extended period of time.
11.4.2 Misc. Engineering Tips
A Single EMS can support up to twelve (12) HA ASBCE instances, or 24 singles (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 a 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
11.4.3 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.1.1 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 R7.2.2. Remote
worker capabilities with any of the J139/169/179 phones require the ASBCE R7.2.2.
• 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.
12 Product Licensing Process and Policies
12.1 PLDS licenses
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)
• Premium License (with optional HA) as of 8.1.1
• CES License
• Encryption License
• Signaling only encryption license
• Transcoding License
• Scopia Video License
• Dynamic Licenses

‘Rules of thumb’ for use of the centralized WebLM (most of the time) vs. the co-resident local version:
ASBCE VM Based WebLM System Manager Co-resident WebLM on

Implementation WebLM the ASBCE
Type and
ASBCE Yes Yes Yes
EMS
Appliance
ASBCE Virtual Yes Yes No
EMS Appliance Yes Yes Yes
EMS Virtual Yes Yes No
Product License Distribution System (PLDS) is the Avaya tool for managing and distributing software product
license files for Avaya applications. ASBCE 8.1.1 leverages this tool for the license management and
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 WebLM during the
installation process. PLDS access is required for the Business Partner to activate and retrieve the license
file. PLDS is used for both Enterprise/Aura implementations and 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.
Avaya provides 24/7 support for PLDS in the following countries:

• US/Canada +1 866 AVAYA IT (+1 866 282 9248)
• EMEA +31 70 414 8023
• CALA:
o Argentina +54 11 4114 4901
o Brazil +55 11 5185 6700
o Colombia +57 1 592 2805
o Mexico +52 55 5278 7654
• APAC +65 6872 8700
Avaya Business Partners should refer to the following website for information on access, licenses,
downloads and job aids:
• https://support.avaya.com/support/dashboard.action

12.2 Temporary license Requests
See Avaya Global Temporary License Policy
• Temporary/Emergency licenses up to 30 days for emergency /outages do not require product

management or product operations approval. See Avaya Global Temporary License Policy
• Temporary Licenses are not intended or approved to manage Sales gaps in customer capacity
planning.
• Temporary Licenses are not for Demo/Customer Trials, you must go to Try Avaya for these scenarios
• Temporary licenses between 31-90 days require product management or product operations
approval. Please call the Helpdesk (Tier 3) to request a temporary license.
• Temporary licenses beyond 90 days are not approved.
Avaya Helpdesk:
For the USA, please call 1-866-AVAYA IT (+1-866-282-9248) or 303-354-8999
EMEA users should call +44 1483 309800
Canada and CALA users should call +1 720 444 0130
APAC users should call +65 6872 8700
Germany users should call +49 69 7505 1234
12.3 Lab Trials
Customer lab systems must be ordered and purchased as per standard processes and can leverage the
partners MDF funds.

13 Services and Support
13.1 Pre- Sales Support
To obtain pre-sales support from the ATAC Presales Technicenter:

Please utilize the ATAC FAQ database tool before you engage the Technicenter at
https://avaya.my.salesforce.com/apex/sp_ViewDetailPage?Id=a3ja0000000LXXRAA4
• In NAR, contact ATAC at 720-444-7700 or 888-297-4700 (if toll-free is required) or atac@avaya.com

• In CALA, contact ATAC at 720-444-7700 or 888-297-4700 (if toll-free is required) or
ataccala@avaya.com
• In EMEA, contact ATAC at +44 1483 309078 or atacemea@avaya.com
• In APAC, contact ATAC at +65 6872 2693 or atacapac@avaya.com
• In India, contact ATAC at +91 20 3092 6555 or atacapac@avaya.com
• In Russia, contact ATAC at +7 4995004840 or atacrus@avaya.com
When prompted for what product you want support with speak that product name.
After speaking the product name, you will be given an option for support with an ASD design.
Please remember to include the product category in the email subject line (i.e. Contact Center) for priority
routing and handling.
13.2 Services Support Offers
The major Avaya Services offers for ASBCE 8.1.1 cover all facets of post-sale support for the product. The
offers differ somewhat depending on whether the implementation is one for Enterprise/Aura customers or IP
Office customers. The biggest difference is in the Maintenance Services area, as Enterprise/Aura customers
are served by Support Advantage (SA) while IP Office users a served under IP Office Support Services
(IPOSS). The major Services areas are:
• Avaya Professional Services (APS) and Installation support
• Maintenance Services for software and hardware
• Repair and Return Services
13.2.1 APS and Installation Support
Avaya Professional Services (APS) part of the Sales Organization, provides the vital tools, expertise, and
resources needed to install, integrate, or upgrade a new and existing communications networks. This portfolio
gives Avaya customers the flexibility to select one service or an entire suite of services to match their needs
and technical expertise. APS services are available to perform Installation/deployment for both
Enterprise/Aura customers and IP Office customers. The services noted here are specifically for the ASBCE

itself, Call Server or other applications have their own APS offers and would be ordered specifically for those
products in a broader system installation.
Avaya Deployment Services are available in the following three options:

1. Basic – Avaya will perform the application installation and configuration responsibilities within the
deployment. Hardware installation and overall project management will be provided by the end
customer or business partner. This is also known as “Configuration Only”
2. Standard – Avaya will perform the hardware and software installation as well as configuration
responsibilities within the deployment. Overall project management will be provided by the end
customer or business partner. This is also known as “Installation and Configuration”.
3. All Inclusive – Avaya will perform the hardware, software installation as well as configuration
responsibilities within the deployment. Overall project management will also be provided by Avaya.
This is also known as “Planning, Design, Installation, and Configuration.”
The ordering customer chooses among these offers as part of building the SSR or PRM order to APS.
APS is mission is "We will provide the best and most knowledgeable sales support needed to beat the competition, win
sales, and delight our customers."
13.2.2 Customer Care/Support

The Avaya Techni center provides Business Partners with presales technical system features, function and
design support.
From self-service using our online knowledgebase through live, personal assistance from a subject matter
expert, we are focused on delivering accurate, up-to-date pre-sales technical support for Avaya products.
The Techni center is part of Sales Support & Technical Operations.
The Avaya Techni center has launched a self-service FAQ tool, accessible by Avaya associates and
Business Partners, for quick access to pre-sales feature functionality technical support information. The self-
service tool is also available for mobile devices for both Avaya and Partners via the Sales and Partner Portals.
Please utilize the FAQ database tool before you engage the Technicenter at
https://avaya.my.salesforce.com/apex/sp_ViewDetailPage?Id=a3ja0000000LXXRAA4
Call or Email Us <<<Please remember to include the product category in the email subject line (i.e. Contact
Center) for priority routing and handling>>>
North America Regional Access

atac@avaya.com* EMEA Regional Access
1 720-444-7700 or 888-297-4700
Hours of Operation: atacemea@avaya.com*
9:00 am-6:00 pm EST Monday-Friday +44 1483 309078
Hours of Operation:
10:00 am-12:00 am CET, Monday-Friday
AI Regional Access
ataccala@avaya.com* APAC Regional Access
1 720-444-7700 or 888-297-4700 atacapac@avaya.com*
Hours of Operation: 91 2030 926555 India
9:00 am-6:00 pm EST Monday-Friday 65 6872 2693 Singapore
Hours of Operation:
4:00 pm to 6:00 am SGT, Monday-Friday

Russian Regional Access atacrus@avaya.com* SMB Pre-Sales Technical Support
+7 4995004840 atac@avaya.com*
Hours of Operation: 1 720-444-7700 or 888-297-4700
10:00 am to 7:00 pm MSK, Monday-Friday Hours of Operation:
9:00 am-6:00 pm EST Monday-Friday
13.2.3 Maintenance Services

Maintenance Services is different between Enterprise/Aura implementations and systems implemented with
IP Office. The biggest difference is in the Maintenance Services area, as Enterprise/Aura customers are
served by Support Advantage (SA) while IP Office users a served under IP Office Support Services (IPOSS).
13.2.3.1 Support Advantage for Enterprise/Aura Customers

Applicable for all new system purchases, Support Advantage provides 24x7 support for both software and
hardware, which helps protect customers’ investments in enterprise communications from Avaya. The offer
has a simple structure with a single base software support offer choice, a hardware support offer and an
upgrade protection support offer:
• Preferred Support:
o Provides 24x7 remote software and hardware support
o Defined response times for major and minor issues
o Access to software updates, services packs and firmware updates
o Basic web services for online support.
o Improved response times for Service Requests submitted via the web
o Includes Secure Access Link Policy Server
o Enhanced support response times.
▪ Response time is defined as the time interval from Service Request creation to
Avaya’s Remote Service Team Member contacting the customer via phone or
email.
▪ Outbound Status Activity is the associated Avaya process step associated with this
action.
• Upgrade Advantage: This is an add-on service sold in addition to Essentials or Preferred software
support as a subscription that runs concurrently with the SA contract. This option allows access to
Major Releases of software that come available during the subscription term. This service does not
imply new hardware or extra software licenses; those are available for separate purchase.
• Hardware Advantage: Provides Advanced Parts Replacement via the following delivery options
(geography dependent):
o Replacement Parts shipped From Repair and/or Logistics centers the Next Business Day.
This service will evolve to align with other core applications as volumes grow, note that this
can impact system outages, particularly for Single Availability (SA) systems.
o Note that care must be taken when offering and not all hardware support options will be
available in all regions due to next business day ship constraints.

For eligibility under the Parts coverage options:
• The Supported Products must be installed and located within a specified driving distance from an
Avaya parts stocking location.
o NOTE: This capability is geography dependent. Parts are not available in each region.
Availability is documented in the Service Agreement Supplement.
Support Advantage availability varies per region. While Support Advantage for ASBCE does not offer Next
Business Day (NBD) onsite with parts, NBD shipment is available.
13.2.3.2 IPOSS for IP Office customers

Customers purchasing ASBCE 8.1.1 for use with IP Office have the option of using IP Office Support Services
maintenance contract for the ASBCE. The IP Office Support Services (IPOSS) offer provides manufacturer
support to maintain and support customers IP Office systems and applications. The Avaya IP Office Support
Services portfolio provides global service options designed to maintain and support IP Office. This portfolio
of services is tailored to meet a wide range of customer needs, by providing a solution- centric approach and
delivering increased value in a flexible and modular support model. These new offers introduce a simplified
quoting and pricing methodology based on node/server with this introductory offer. The Offer is available
globally through an Avaya Single Tier purchasing and the Avaya Two Tier Distribution process in a wholesale
or co-delivery model through Avaya Authorized Partners. Offer Includes:
• Remote technical support for hardware and software
• Access to major and minor software upgrades, software updates/corrective content
• Access to software patches
• Enhanced remote connectivity
Optional Advanced Parts Replacement is available in most regions. However, all shipping is centralized, at
present, in the US. The terms around ‘Next Business Day’ refer to next business day shipping, for example.
Other options include: Business Day Support (8x5x5) or Any Time, Any Day Support (24x7x365).
More information about IPOSS can be found at https://support.avaya.com/css/P8/documents/100164744

and http://support.avaya.com/css/P8/documents/100113905.
IPOSS is required when adding ASBCE 8.x to an existing IP Office IP500v2 (without IPOSS).
Additionally, IP 500v2 stand-alone systems do not require IPOSS. Server Edition*, Select Edition*, IPOCC,
ACCS solutions do require IPOSS.
* And associated IP500v2’s
13.3 Remote Access and Maintenance

Remote access is required between Avaya and ASBCE or else remote maintenance support is not possible.
Two means of remote access can be used, with the choice depending on the market segment served. Larger
Enterprise customers utilize Secure Access Link (SAL), which is described in documents on the Support
Portal. Small to Medium Enterprise (SME) customers using ASBCE in a solution with IP Office 9.x (or above)

will typically use SSL VPN to connect to Avaya.
Alternatively, Avaya partners and/or customers may decide to install and activate the HP iLO service or Dell
iDrac on the ASBCE appliances supporting it (see hardware section of this document) to monitor the
hardware performance.
13.3.1 SAL Remote Access for Enterprise/Aura Customers

Avaya Secure Access Link (SAL) is the primary IP-based remote access and alarming solution for Avaya
products. SAL offers Avaya customers a secure, software-based solution that gives them complete control
over their environment with respect to remote access and alarming for their Avaya products. With Secure
Access Link and its centralized management design, customers can now decide who and when their products
are accessed remotely, as well as control which products can alarm out. Once deployed, the Secure Access
Link solution is then able to extend and establish a secure relationship with Avaya’s backend infrastructure,
which allow Avaya services to securely manage and maintain their Avaya products.
For Avaya ASBCE 6.2 FP1 and later, SAL is supported for remote access.
The remote monitoring and alarming services are available since ASBCE 7.1 and later. SAL access is
required, and an Enterprise/Aura customer’s existing SAL gateway can be used to support SAL remote
access to the Avaya ASBCE.
13.3.2 SSL VPN Access for IP Office customers

IP Office SSL/VPN solution is a fast and easy method to setup a secure remote access at broadband speed.
This solution is designed to provide partners benefits to streamlined serviceability options to their end-
customers. The solution enables business partners to create an infrastructure that automates management
and maintenance of their customers’ IP Office CPE devices as well as other application servers on the
customers’ LAN side. The solution is geared toward providing the ability to Avaya partners to set up their own
Network Operations Center (NOC) at a reasonable price, and a solution that is simple to use.
The IP Office SSL/VPN solution offers a secure remote accessibility to the IP Office CPE devices with
minimum networking expertise needed to set up the CPE at the customers’ sites. It can also be pre-
configured with SSL-VPN configuration before it is installed on the customers’ sites.
13.3.3 iLO and iDRAC with ASBCE hardware appliances

As mentioned in the head of this chapter, iLO (integrated lights out from HP) and iDRAC (Integrated Dell
Remote Access Controller from Dell) features can be activated on the ASBCE hardware appliances that
support it (see hardware section in this document).
iLO and iDRAC are not supported on the Portwell Appliances
The iLO and iDrac licenses and services will have to be directly obtained and licensed from the proper
channels as Avaya does not resale such license with the current set of appliances.
The setup of this service on the ASBCE appliances and the associated backend configuration is entirely the
responsibility of the customer or partner. Avaya responsibilities is limited to guaranteeing that these services
are not interfering with the normal functioning of the ASBCE appliance.

13.4 PCN/PSN Strategy
13.4.1 Product Correction Notice (PCN)

Product Correction Notices (PCNs) are issued when a product’s functionally deviates in any material respect
from product documentation that Avaya generally makes available to users of its products. Deviations
normally affect multiple customers and fall into three different severity levels; class 1 being the most severe
through class 3 representing corrections for minor issues. Severity levels are used to determine appropriate
notification action and to guide service providers, resellers and customers on appropriate implementation
actions. Customers, distributors, and dealers will receive proactive notification for Class 1-2 by registering on
the Customer Support web site and subscribing for PCNs. Class 1-2 notices will also be available to view on
the Customer Support web site. Partners and Avaya associates will continue to be able to view additional
pertinent PCN information on their respective Partners and Avaya associate web sites. The standard PCN
process applies for this product.
13.4.2 Product Support Notice (PSN)

Avaya will, when required and time-to-time, issue/post technical product bulletins call Product Support
Notices (PSN). Avaya associates, Partners and end customers use these notices to stay informed about
emerging technical issues and other technical support information regarding products, documentation,
licensing, and process. These notices take the place of the Services Alert, now discontinued.
13.5 Technical Consulting System Support

Avaya provides help line support. To obtain additional support Please call ATAC Pre-sales, Sales and
Technical support at 720-444-7700 or 888-297-4700 ( US and AI ) , 720-444-7700 (CALA) or 44 183
309078 (EMEA) or 65 6872 2693 (APAC) or send email to atac@avaya.com .
You can also use the interactive support features available online to Open a Service Request, chat with a
LIVE agent and more by selecting the specific link associated with your country.
https://support.avaya.com/contact/
Avaya provides help line/maintenance support to customers that have purchased a Post Warranty
Maintenance agreement.
The Avaya GSS Management Escalation Activity (MEA) Process provides a means to engage our
management team to help manage your open service request issue with the appropriate technical resources
and the proper sense of urgency.
13.6 Enhanced Services Available
13.6.1 Avaya Operations Services – UC Managed Assist and UC Managed

Operate
Avaya Operations Services (AOS) team provides full management services capabilities to customers,
allowing them to focus on their core business. Service capabilities provided in managed services offers

include, but are not limited to:
• Single point of entry for system administration and fault management
• General usability help line support
• 8 x 5 local site time maintenance
• Standard service level agreements
• Performance reporting
• Engagement Manager assigned for the term of the Agreement
• Program management of all communications projects
• Single monthly invoice with multi-level data
Pricing is structured into monthly recurring charges on a per port basis, plus additional charges for services
such as special projects and MACs (moves, additions, and changes). More information on UC Managed
Operate and UC Managed Assist offers can be found at URLs
https://avaya.my.salesforce.com/069a0000002ifuS
https://avaya.my.salesforce.com/069a0000002ifvV
13.6.2 Remote Configuration Helpline (RCH)

During the applicable service period, Avaya provides helpline support to customers which includes answering
any general usability questions regarding software or products and providing advice to help the customer
achieve a working solution. This includes directing customers to sections of the documentation that may
answer their question(s), clarifying the documentation, or recommending possible training courses. The
Remote Configuration Helpline’s assistance does not include help with design or customer LAN issues.
Customer specific programming, administration, and training support can be provided to the customer at
Time and Material rates. Alternately, support can be purchased through the Block of Time program.
Customers may call one of the phone numbers that follows, 7x24:
United States and Canada +1-800-225-7585
Other countries +1-720-44-GLOBE (45623)
Countries other than U.S., Canada, Caribbean, Latin America, and Asia Pacific:
Other international customers receive help line support from their channel partner under the terms
and conditions established with and by the channel partner. Customers who purchased product
directly from Avaya receive help line support from the in-country call receipt team.
13.6.3 Remote Access via Secure Access Link Gateway

System Manager provides secure, rapid serviceability and Expert Systems alarm handling through Secure
Access Link (SAL) to Avaya. SAL uses the customer’s existing Internet connectivity to facilitate remote
support. All communication is outbound from the customer’s environment using encapsulated Hypertext
Transfer Protocol Secure (HTTPS). SAL requires upload bandwidth (customer to Avaya) of at least 720 kbps
with latency no greater than 150ms (round trip).
A VMware OVA with SAL Gateway 2.5 (or later) is offered as part of every Appliance Virtualization Platform
(AVP) 7.x. Customers may install the SAL Gateway 2.5 OVA on AVP 7.x to manage up to 15 Avaya products
installed on that AVP and elsewhere in the enterprise. If more than 15 Avaya products are present in the
enterprise, the customer should install a standalone, full-scale SAL Gateway capable of managing up to 500

Avaya devices. The full-scale SAL Gateway is included in the Avaya Diagnostic Server 2.5 packages.
Important: Business Partners and customers must ensure that SAL is always configured and registered with
Avaya during installation. Avaya support will be delayed or not possible if SAL is improperly implemented or
not operational. Modem connections are not supported.
13.6.4 Remote Diagnostics via Avaya Diagnostic Server

Avaya Diagnostic Server consists of the SAL Gateway and Service Level Agreement Monitor (SLA Mon).
The SAL Gateway is used to provide remote support to all Avaya customers. SLA Mon is a free entitlement
to Support Advantage Preferred customers. The software package and installation utility are designed to
install one or both components, as needed.
SLA Mon is an on-premise tool that offers two sets of features: Endpoint Diagnostics and Network Monitoring.
With Endpoint Diagnostics a customer can remotely control and diagnose 9600 Series IP Desk phones. With
Network Monitoring a customer can use intelligent agents embedded in Avaya products to monitor up to 250
network paths for packet loss, jitter, delay, and QoS. SLA
SLA Mon entitlement check and license distribution for Support Advantage Preferred customers is handled
via a license request form. A 30-day trial period is offered to customers who currently do not have Support
Advantage Preferred. The 30-day trial is built into the software and begins upon installation of SLA Mon. For
more information on Avaya Diagnostic Server and SLA Mon, go to https://support.avaya.com/ads.
Avaya Diagnostic Server (SAL + SLA Mon) is supported through the Avaya Client Services Backbone team.
Start by opening a web ticket on https://support.avaya.com for assistance.
13.7 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.
13.7.1 Post Warranty support

Customers may purchase post-warranty support for the Avaya Aura® product components after the
expiration of the initial warranty. Please see Support Advantage details at
https://avaya.my.salesforce.com/apex/sp_ViewDetailPage?c=a3d30000000L2cpAAC&Id=a3j30000000L3j
AAAS
Warranty on parts is available worldwide, but servicing terms and conditions may vary subject to locations
where Avaya service is offered.
13.8 Repair & Return, Logistics

Repair and Return processes for ASBCE 8.1.1 follow Avaya’s general processes. There are differences
between the US and other countries.
Logistics refers to the process that provides parts in support of the Service Process. The key to logistics is
having the right part in the right place to replace the defective element in a period consistent with intervals
provided in the Service Offer. Details below explain the full built-out, longer-term strategy.

Within the US:
When the customer experiences defective components under warranty or maintenance terms, they
should contact their Avaya representative for replacement. In the U.S., the Avaya representative
contacts the GSS at 800.242.2121 to obtain a trouble ticket. When Hardware troubles are confirmed,
the Avaya representative inputs the ticket within SAP and orders the equipment. The OSA arranges
for Refurbished Material where available and New Materials when necessary to be sent to the
customer by creating a “-651 DEFECTIVE” shipment to the customer. Customers who are currently
within the warranty period receive the components at no charge.
For Countries other than the US:

In other countries, upon advice of the warranty claim by an Account Executive, technician, or other
qualified associate, the OSA creates a NEW SAP order for the replacement or defective item. The
NEW SAP order number is made to match the customer’s original P.O. number with an additional
suffix referred to as the “Pro forma Reason Code.” There are several different Pro forma Reason
Codes, which have the intent of quickly identifying (to internal users) the reason for the claim; e.g.,
“SS” = short shipment; “O” = overage; “DOA” = defective on arrival; etc. Please note that warranty
items are first supported with refurbished goods before new ones. The return of the displaced
equipment needs to be described, ensuring return to Avaya.
13.8.1 Dead on Arrival (DOA)/Out of Box Failure (OBF)

DOA and Return forms can be found at:
https://enterpriseportal.avaya.com/ptlWeb/internal/spCP/CS2004121220312151039.
14 Avaya DevConnect
It remains critical for sales and pre-sales associates to understand the GSSCP (Global SIP Service Provider
Compliance Program), and the need to ensure that the customer’s SIP trunk provider has completed testing
within this process before deploying that customer. If not, this will impact the extent and nature of Avaya
Global Services’ ability to support the customer’s implementation.
More information about the DevConnect and SIP interoperability can be found at:
https://www.devconnectprogram.com/site/global/products_resources/avaya_ASBCE/overview/index.gsp
The latest list of certified ITSPs can be found under:

https://www.devconnectmarketplace.com/marketplace/search?categories=34&tags=118
15 Contact Information
If you have questions regarding the Avaya Aura® Solution, please contact ATAC at North America +1 720
444 7700 EMEA +44 1483 309078 APAC +65 6872 2693 +91 20 3092 6555
Email: ATAC@avaya.com with the product in the subject line (E.g. ASBCE) or go to
https://atac.avaya.com/Technicenter.asp

(Hours of operation: 9 am EST – 8 pm EST) before contacting the responsible Product Manager(s) below.
For RFA related issues, please contact the RFA help Desk at 866-282-9248.
For a current listing of product managers, the Product Management Directory can be found at:
https://sales.avaya.com/en/general/product-management-directory
Avaya ASBCE Product Management Team

Christine McKenna, Suites, PPU, cmcken@avaya.com
Jerome Joanny, ASBCE, jmjoanny@avaya.com
For escalation: Paul Relf Product Management Sr Director, paulre@avaya.com


SBCE 8.1.1 Offer Definition

Uploaded by

Copyright:

Available Formats

You might also like

SBCE 8.1.1 Offer Definition

Uploaded by

Document Information

Original Description:

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

SBCE 8.1.1 Offer Definition

Uploaded by

Copyright:

Available Formats

__________________________________________________________________________________________________

Avaya Session Border Controller

© 2020 Template Rev 1.0 Avaya Inc. All Rights Reserved.

Avaya Inc. – Proprietary. 1

Product ➔ Avaya ASBCE® 8.0, 8.0.1, 8.1 GA Date ➔ 08/04/2020

Avaya Source Prime Channel Partner Target Audience

Avaya Inc. – Proprietary. 2

2 Avaya Session Border Controller for Enterprise solution ...................................................................................... 7

Avaya Inc. – Proprietary. 3

9 Avaya Learning .......................................................................................................................................................... 58

10 Product Ordering, Licensing and Pricing ............................................................................................................... 67

Avaya Inc. – Proprietary. 4

13 Services and Support ................................................................................................................................................ 95

Avaya Inc. – Proprietary. 5

Avaya Inc. – Proprietary. 6

Key trends in the Enterprise communications market are:

Avaya Inc. – Proprietary. 7

Avaya Inc. – Proprietary. 8

3 About ASBCE 8.1.1

3.1 Why upgrade to ASBCE 8.1.1

The key features delivered so far in Release 8.x are:

Avaya Inc. – Proprietary. 9

And finally, the Technology currency elements:

3.1.1 Extended Manufacturer Software Support Release

Once a release has been designated as EMSS, Avaya will

Avaya Inc. – Proprietary. 10

The solution is composed of four main components:

Avaya Inc. – Proprietary. 11

3.3 ASBCE deployment options

3.3.1 Virtualized environment

3.3.2 Avaya Virtualization Platform (AVP) [8.0.1]

Avaya Inc. – Proprietary. 12

3.3.3 Server Appliance (not virtualized aka Bare metal)

Avaya Inc. – Proprietary. 13

Avaya Inc. – Proprietary. 14

Specification Low Range ASBCE(Portwell) Mid-Range ASBCE High Range ASBCE

3.3.3.2IP Office / Mid-Market

Avaya Inc. – Proprietary. 15

Specification Low Range ASBCE Mid-Range ASBCE

Specification Low Range ASBCE Mid-Range ASBCE

Maximum Current (110V) 0.5 A 2A

3.3.4 Discontinued Hardware appliance with Release 8

Avaya Inc. – Proprietary. 16

3.3.5 Cloud Deployments

3.3.6 Discontinued Virtualization platform support with Release 8

Avaya Inc. – Proprietary. 17

4.2 Business Partner Value Proposition

Avaya Inc. – Proprietary. 18

4.2.2 Value Proposition

Avaya Inc. – Proprietary. 19

4.2.3 Defensible Differentiators

Avaya Inc. – Proprietary. 20

4.2.4 Partner Business and Strategic Value

Avaya Inc. – Proprietary. 21

4.2.4.2 Mid-market Use Cases

• SIP trunking to Carrier networks and IP Office.

Avaya Inc. – Proprietary. 22