New in Communication Manager Release 10.2

Last Updated : Jan 08, 2024 |

With Release 10.2, Avaya Aura® Communication Manager supports the following new features and enhancements:

Support for VMware 8.0

With Release 10.2, Avaya Aura® applications support the VMware® vSphere ESXi 8.0 and VMware® vCenter Server 8.0 in a VMware virtualized environment.

Support for Trellix AV (formerly known as McAfee) in Virtualized Deployments

Avaya Aura® Release 10.2 supports the deployment of Trellix AV software in a virtualized (OVA-based) environment. This new feature effectively detects, prevents, and eliminates malware threats, resulting in enhancing the security of your Avaya Aura® environment. The IT industry widely recognizes Trellix AV as a trusted cybersecurity solution. With the integration capabilities in Avaya Aura® Release 10.2, you can seamlessly integrate Avaya Aura® applications as managed devices as part of your existing Trellix deployment. For more information on support of Trellix for AV on Avaya Aura®, see Application Note for Support of Trellix AV on Avaya Aura® on the Avaya Support website at https://support.avaya.com.

Support for J139, J159, J189, and J189CC endpoints

With Release 10.2, Communication Manager supports the following J-Series endpoints: J139, J159, J189, and J189CC.

To administer these endpoints, use System Manager.

When you add these endpoints from System Manager, Communication Manager displays these endpoints in the Type field of the Station form as AvyaSIP or AvyaSIPCC, and the actual endpoint type, such as J139 and J159, appears in the Actual field.

Edge Friendly Branch Survivability

In the previous Avaya Aura® Release 10.1, support for Edge Friendly Branch Survivability feature was introduced, which made it easier to have seamless connections between your on-premise G4xx Gateways and the Core Communication Manager hosted on the Cloud. Avaya designed this innovation to protect your investments, especially when you are considering a shift to a Cloud-based infrastructure.

With Avaya Aura® Release 10.2, migrating to the Cloud is even more streamlined. You can now configure edge topology for Cloud deployment. Survivable components like Local Survivability Processor (LSP) and Branch Session Manager (BSM) within G4xx Gateways can connect to Core Communication Manager and Session Manager on the Cloud. This connection between Gateways and Cloud can be established over the Internet or through SD-WAN, providing significant advantages in terms of Total Cost of Ownership (TCO).

To configure LSP topology to edge, do the following:
  • Download TLS certificates to the new Edge Topology (E) repository. The certificates are required to set up a new WebSocket connection between the main Communication Manager and the Communication Manager LSP.

  • On the Communication Manager SMI, go to Administration > Server (Maintenance) > Server Configuration > Server Role page and configure the LSP Topology Configuration section.

  • On the main Communication Manager SAT, go to the change survivable-processor screen and do the following:

    • Configure the LSP topology as Edge.

    • In the Serial Number field, enter the serial number of Communication Manager LSP.

Line Load Control (LLC) feature enhancement

In previous releases, you must configure LLC using System Manager or Communication Manager SAT only, but now you can easily configure LLC using Feature Access Codes.

Avaya Aura® Release 10.2 enhances the LLC feature for enhanced security. It provides an option to implement two-factor authentication for LLC setup, requiring the entry of a security code, which strengthens the security process.

In Avaya Aura® Release 10.2, you can limit the scope of LLC at the site level of your organization. It means that LLC can be applied selectively, exclusively to users of your organization associated with the site from which you initiated the LLC. It offers a more precise and site-specific approach to LLC deployment, enhancing the flexibility and control over LLC configurations.

Support to record the call originated from bridged line appearances

Communication Manager's Bridged Appearance feature is a widely used feature in both Unified Communications (UC) and Contact Center (CC) environments. In previous releases, a call originated using bridged appearance in a SIP environment was never recorded. This gap is addressed in this current release.

With Release 10.2, Avaya Aura® sends the required events for recording over Adjunct Switch Applications Interface (ASAI) when the call is initiated using Bridged Appearance.

Mask CLI and Station Name support on SIP

In Release 10.2, Avaya Aura® further enhances its functionality by extending the capability to mask the calling party number and name on outgoing calls. You can achieve this functionality using the send-nn button on SIP Phones. This feature enables your organization to keep the caller's identity confidential, thus enabling the implementation of a standardized approach for callback interactions.

Alerting internal users with a tone during external communications

In Release 10.2, Avaya Aura® introduces a security enhancement that notifies internal users with an audible tone when they are communicating with external parties. This unique tone is heard only by internal users. You can adjust the time interval between these tones through the System-Parameter Features form. Additionally, you can apply this feature to selective trunk groups, ensuring it operates only on the configured trunk groups.

STIR/Shaken support for verification level display on phones

STIR/Shaken is a set of protocols designed to counter caller ID spoofing on public telephone networks. Avaya Aura® Release 10.2 supports STIR/Shaken and enables the display of the attestation or verification level set by service providers on user or agent phones. This feature works exclusively over SIP trunks. You can enable or disable this feature at the Avaya Aura® solution level based on your preferences.

New field added to the Coverage path page

With Release 10.2, the Description field is added to Coverage path page. You can use the Description field to specify a name for a coverage path to distinguish the coverage paths.

Discontinued support of legacy technologies

Avaya Aura® Release 10.2 discontinued the following legacy technologies to reduce the risk to Business Continuity for customers:
  • G650 or any cabinet/Gateway that connects to Communication Manager using IP Server Interface (IPSI) is no longer supported. For more information, see the End of sale G650 document published on the Avaya Support website.

  • VMware ESXi version 6.7 or lower versions are not supported.

  • Avaya Device Adapter Snap-in is no longer supported.