Avaya Session Border Controller for Enterprise (ASBCE) can be deployed on the Kernel-based Virtual Machine (KVM) infrastructure. KVM is a virtualization technology that allows multiple operating systems to run on a single physical machine. To deploy ASBCE on KVM, you need to use a template file that contains the ASBCE software image and configuration parameters. The template file type to be used for KVM deployment is QCOW2, which stands for QEMU Copy-On-Write version 2. QCOW2 is a file format for disk images that can be used by QEMU, which is an open source emulator and virtualizer that can run KVM virtual machines. QCOW2 files support features such as compression, encryption, snapshots, and backing files

The Avaya Session Border Controller for Enterprise (ASBCE) provides an integrated (local) WebLM server that can be used to install and manage licenses for the ASBCE server. The local WebLM server is only supported in a single-server hardware-based deployment, which is a deployment where the ASBCE server runs on a dedicated hardware appliance, such as an Avaya SBCe 1U or 2U server. In this deployment, the local WebLM server runs on the same hardware appliance as the ASBCE server and can be accessed using the ASBCE web interface or CLI. The local WebLM server can store up to 10 license files and can handle up to 5000 concurrent sessions.

When deploying the Avaya Aura® Presence Services on Avaya Breeze®, you can check the status of the Presence Services snap-in in System Manager, under Elements > Avaya Breeze> Service Management > Services. The status indicates the state of the snap-in on the Avaya Breeze® cluster. The status Active means that the snap-in is running and ready to support Presence and IM. The other statuses are either intermediate or error states that indicate that the snap-in is not fully functional or operational.

To provide the customized music, prompts, and/or error announcements when using the Avaya Call Park and Page snap-in, you need to use the Avaya Aura® Media Server (MS). The Media Server is an application that provides media processing services for voice and video calls, such as playing announcements, music on hold, conferencing, transcoding, and recording. The Media Server can be integrated with the Call Park and Page snap-in on the Avaya Breeze® platform, using SIP trunks and media resources. You can upload your own audio files to the Media Server and configure them as custom announcements for the Call Park and Page snap-in34

If the Avaya Session Border Controller for Enterprise (ASBCE) does not trust the Certificate Authority (CA) that signed the WebLM server identity certificate, you can use the sbceconfigurator.py fix-weblm-cert command issued from the EMS CLI to fix the trust issue. The WebLM server is a web-based licensing application that manages licenses for various Avaya products, such as Communication Manager, Session Manager, Presence Services, or Breeze Platform. The WebLM server uses an identity certificate to authenticate itself to other entities that communicate with it using HTTPS or REST APIs. The identity certificate is signed by a CA, which is an entity that issues and verifies certificates. The ASBCE server needs to trust the CA that signed the WebLM server identity certificate in order to communicate with it securely and obtain licenses from it. If the ASBCE server does not trust the CA, you can use the sbceconfigurator.py fix-weblm-cert command to install the CA certificate on the ASBCE server and establish trust with it. The sbceconfigurator.py tool is a Python script that runs on the EMS component of the ASBCE server and performs various configuration tasks. The EMS component is responsible for managing and monitoring the ASBCE server. You can access the EMS CLI using SSH or Telnet and run the sbceconfigurator.py tool from there.

In some deployments, you can enable a feature called “Stream Users Over Transport Link” in the Signaling Interface used for the Avaya Aura® Session Manager (SM) on the Avaya Session Border Controller for Enterprise (ASBCB). This feature allows reusing the same TCP connection to SM for all SIP messages related to Remote Workers registered with SM through ASBCB. A Signaling Interface is a configuration object that defines how ASBCB handles SIP signaling with other entities, such as endpoints or servers. A Signaling Interface can include parameters such as source and destination IP addresses, ports, protocols, encryption modes, authentication modes, and timers. The “Stream Users Over Transport Link” parameter is an option that can be enabled or disabled in the Advanced tab of the Signaling Interface configuration screen. When this option is enabled, ASBCB will use the same TCP connection to SM for all SIP messages related to the same Remote Worker. This can reduce the number of TCP connections and improve the performance and scalability of ASBCB and SM.

Avaya Aura® Presence Services does not require a separate license file or an instance license. User licenses are an entitlement as part of the Avaya Aura® suite licensing, such as Foundation, Mobility, Team Engagement, or Customer Engagement. The user licenses are consumed based on the number of users who are provisioned for Presence Services in System Manager

When creating a SIP Entity for Avaya Breeze® hosting the Avaya Aura® Presence Services, you need to enter the IP address or FQDN of the Avaya Breeze® server Security Module (SM100) in the field labeled IP Address. The SM100 is a component of the Avaya Breeze® server that provides security and encryption functions for SIP signaling and media. The SM100 IP address or FQDN is used by the Presence Services snap-in to communicate with other SIP entities in the network, such as Session Manager or Communication Manager

To allow communications between the Avaya Aura® Device Services (AADS) and the Avaya Aura® Web Gateway (AAWG), you need to perform the following configuration steps:

• Configure the AAWG FQDN as a Trusted Host on the AADS: A Trusted Host is an entity that is allowed to communicate with the AADS server using HTTPS or REST APIs. You need to configure the Fully Qualified Domain Name (FQDN) of the AAWG server as a Trusted Host on the AADS server, using the System Manager web interface. This allows the AAWG server to access the AADS server for device management and configuration purposes3
• Configure the AADS FQDN as a Trusted Host on the AAWG: Similarly, you need to configure the FQDN of the AADS server as a Trusted Host on the AAWG server, using the app configure command line utility. This allows the AADS server to send dynamic configuration parameters and certificates to the AAWG server for WebRTC call signaling and media processing4
• Configure the AADS FQDN, Client interface port and Server-to-server interface port on the AAWG: You also need to configure the FQDN, Client interface port and Server-to-server interface port of the AADS server on the AAWG server, using the app configure command line utility. These parameters are used by the AAWG server to establish secure connections with the AADS server for device management and configuration purposes. The default Client interface port is 9443, while the default Server-to-server interface port is 84434

Avaya Breeze® is a development platform that enables rapid development for applications targeted to meet a customer’s communications needs. It is used by Avaya, Partner, and third-party developers to create and deploy snap-ins, which are modular software components that provide specific functionality or features. Avaya Breeze® allows application developers to quickly add new capabilities to their Avaya solutions, such as voice, video, messaging, presence, collaboration, and analytics.

To connect the Avaya Breeze® platform that is hosting an Avaya Aura® Presence Services snap-in with the Avaya Aura® Session Manager (SM), you need to configure the following:

• One Entity Link from SM to Avaya Breeze®: This is a SIP trunk that connects the SM and the Avaya Breeze® server for SIP signaling and media. You need to create an Entity Link in System Manager, under Elements > Routing > Entity Links, and specify the IP address or FQDN of the SM and the Avaya Breeze® server Security Module (SM100). You also need to select TLS as the SIP Link Transport Type56
• TLS ports 5061 and TLS 5062: These are the ports used by the Entity Link for secure SIP signaling between SM and Avaya Breeze®. Port 5061 is used by SM to send SIP requests to Avaya Breeze®, while port 5062 is used by Avaya Breeze® to send SIP responses to SM. These ports require a valid certificate on both SM and Avaya Breeze® servers56
• UDP port 5060 and TLS port 5061: These are the ports used by the Presence Services snap-in for XMPP federation with other XMPP servers or clients. Port 5060 is used for unencrypted XMPP traffic over UDP, while port 5061 is used for encrypted XMPP traffic over TLS. These ports enable presence and instant messaging features across different domains or platforms34

To allow the Avaya one-X® Communicator to subscribe to the Avaya Aura® Presence Services, you need to enter the Avaya Breeze® server Security Module IP Address or FQDN in the IM and Presence / Server field of the one-X® Communicator. The Security Module (SM100) is a component of the Avaya Breeze® server that provides security and encryption functions for SIP signaling and media. The SM100 IP address or FQDN is used by the one-X® Communicator to communicate with the Presence Services snap-in on the Avaya Breeze® server and receive presence and instant messaging features.

To access the TSAPI Test from the Application Enablement Services (AES) menu, you need to select Utilities. The TSAPI Test is a basic application for making a call using TSAPI, which is a high-level API for CTI applications based on CSTA I standard. TSAPI allows access to the third party call control capabilities of CM through AES. The TSAPI Test application can be used to verify that the TSAPI client is correctly installed and working on AES. If the TSAPI Test application fails to make the call, an error message is provided to aid in troubleshooting the cause of the failure. To access the TSAPI Test from the AES menu, you need to follow these steps:

• Log in to the web interface of AES using your username and password.
• Click on Utilities on the left side menu.
• Click on TSAPI Test under Utilities.
• Enter the parameters for making a call, such as device name, destination number, user ID, and password.
• Click on Make Call.

The output from the show mgc command (issued on a G430/G450 Gateway CLI) can indicate whether the G430/G450 is operating as an Internet Friendly (Edge) Gateway or an Enterprise Gateway. An Internet Friendly (Edge) Gateway is a device that provides secure and reliable connectivity between endpoints on different networks, such as the public internet and a private enterprise network. An Enterprise Gateway is a device that provides connectivity between endpoints on the same network, such as a LAN or a WAN. The show mgc command displays information about the Media Gateway Controller (MGC), which is the entity that controls the media gateway functions of the G430/G450, such as call processing, routing, and signaling. The MGC can be an Avaya Communication Manager (CM) server or an Avaya Session Border Controller for Enterprise (ASBCE) server. The output from the show mgc command includes these fields:

• Management Link Mode: This field indicates how the G430/G450 communicates with the MGC for management purposes, such as configuration, monitoring, and troubleshooting. The possible values are Direct or Tunnelled. Direct means that the G430/G450 communicates with the MGC using a direct IP connection over TCP port 5022. Tunnelled means that the G430/G450 communicates with the MGC using a tunnel over TCP port 2944 and secured using TLS. This mode is used when the G430/G450 operates as an Internet Friendly (Edge) Gateway and communicates with ASBCE as the MGC.
• H.248 Link Mode: This field indicates how the G430/G450 communicates with the MGC for media gateway control purposes, such as controlling media streams, allocating resources, and creating connections. The possible values areEGW or IFG. EGW means that the G430/G450 communicates with the MGC using H.248 protocol over UDP port 2944. This mode is used when the G430/G450 operates as an Enterprise Gateway and communicates with CM as the MGC. IFG means that the G430/G450 communicates with the MGC using H.248 protocol over TCP port 2944 and secured using TLS. This mode is used when the G430/G450 operates as an Internet Friendly (Edge) Gateway and communicates with ASBCE as the MGC.
• H.248 Link Status: This field indicates whether the H.248 link between the G430/G450 and the MGC is up or down, and whether it is encrypted or not. The possible values are UP/Encrypted, UP/Unencrypted, DOWN/Encrypted, or DOWN/Unencrypted. UP means that the H.248 link is established and functional. DOWN means that the H.248 link is not established or not functional. Encrypted means that the H.248 link is secured using TLS encryption. Unencrypted means that the H.248 link is not secured using TLS encryption.

Therefore, to determine whether the G430/G450 is operating as an Internet Friendly (Edge) Gateway or an Enterprise Gateway, you can look at these two fields in the output from the show mgc command:

• If the H.248 Link Mode displays IFG, it means that the G430/G450 is operating as an Internet Friendly (Edge) Gateway and communicating with ASBCE as the MGC using H.248 over TCP port 2944 and secured using TLS.
• If the H.248 Link Status displays UP/Encrypted, it means that the G430/G450 is operating as an Internet Friendly (Edge) Gateway and communicating with ASBCE as the MGC using a secure and functional H.248 link.

When configuring a Topology Hiding Profile associated with a Session Manager in a typical Avaya Session Border Controller for Enterprise (ASBCE) deployment, you should overwrite the following three SIP headers with a SIP domain: From, Refer-To, and To. A Topology Hiding Profile is a configuration object that masks the FQDN or IP address portion of SIP headers to hide the internal topology of the network. For example, SBCE@avaya.com can become SBCE@135.122.18.7, or just the opposite. The From header indicates the identity of the originator of a SIP request or response. The Refer-To header indicates the identity of the recipient of a REFER request, which is used to transfer calls or sessions. The To header indicates the identity of the intended recipient of a SIP request or response. These headers should be overwritten with a SIP domain to prevent exposing internal FQDNs or IP addresses to external entities

An Application Rule is a type of Domain Policy Rule in the Avaya Session Border Controller for Enterprise (ASBCE) that allows setting a limit to the maximum audio sessions per endpoint, enabling the ASBCE to reject the call when this limit is reached. A Domain Policy Rule is a configuration object that defines the security and quality of service policies for SIP domains that are managed by the ASBCE server. There are four types of Domain Policy Rules: Security Rule, Border Rule, Application Rule, and Media Rule. An Application Rule is a Domain Policy Rule that defines the application-level policies for SIP domains, such as call admission control,bandwidth management, session timers, and session limits. An Application Rule can include a parameter called Max Audio Sessions Per Endpoint, which specifies the maximum number of concurrent audio sessions that an endpoint can have within a SIP domain. If an endpoint tries to initiate or receive more audio sessions than this limit, the ASBCE server will reject the call with a 403 Forbidden response.

The Survivable Communication Manager (CM) is configured on the System Manager (SMGR) as a Managed Element. A Managed Element is an entity that can be managed by SMGR, such as Communication Manager, Session Manager, Presence Services, or Breeze Platform. A Survivable CM is a Communication Manager instance that provides local call processing and trunking capabilities for remote sites or branches in case of a WAN outage or loss of connectivity with the core servers. A Survivable CM can be deployed on an S8300D server or on an external server such as Dell R620/R630 or HP DL360 G8/G9. To configure a Survivable CM as a Managed Element on SMGR, you need to specify its name, type, IP address, login credentials, and security settings56