Device, Media, and Call Control licensing

Last Updated : Feb 02, 2023 |

The Device, Media, and Call Control (DMCC) Service provides control of devices and media streams and a subset of third-party call control services.

DMCC Device and Media Control Service

Historically, licensing for registering a DMCC (formerly CMAPI) station was in the Communication Manager license file, via the IP_API_A field. For customers who had previously purchased those licenses, the IP_API_A licenses will continue to remain accessible by AE Services applications, regardless of which AE Services release the server is running.

Factoring in release levels: In certain circumstances, purchases of new or add-on DMCC licenses are reflected in the AE Services license file as well as in the IP_API_A on Communication Manager, literally doubling the quantity of DMCC Basic licenses with every order.

For customers who have existing licenses in IP_API_A and then purchase additional DMCC licenses, the information provided above about factoring in release levels continues to apply. Effective with Communication Manager Release 6.0, all new DMCC licenses will be added only to the AE Services license file VALUE_DMCC_DMC field.

Upon a registration request, AE Services will first attempt to consume a DMCC license from the AE Services license file. If these are exhausted, AE Services will look to IP_API_A for additional licenses to consume.

Note:

Contact your Account Team to reconcile any DMCC double licensing.

Note:

Regardless of whether DMCC registrations are licensed on Communication Manager or on AE Services, the addition of a DMCC station on Communication Manager also consumes an IP_STA license and an STA license.

DMCC Call Information Service

Licenses are not required to use the DMCC Call Information Service.

DMCC Call Control Service

To use the DMCC Call Control Service, you must license and enable Computer Telephony Adjunct Links on Communication Manager. Because the DMCC Call Control Service uses third-party call control, the AE Services TSAPI Basic Users license is also required.

DMCC/CMAPI Double Licensing Reconciliation Process

When Application Enablement Services (AES) was deployed on Communication Manager (CM) releases prior to 6.x, DMCC Basic (formerly known as CMAPI Basic) licenses were also included in the CM license file as IP_API_A licenses as well as in the AE Services license file for compatibility reasons. This meant Avaya literally doubled the quantity of DMCC Basic licenses with every order which still continues today (for example AE Services 6.3.3 deployed on a CM 5.2.x). This is creating a discrepancy between the customer’s quantities purchased and the actual licenses in place and should be reconciled when the customer’s CM release is upgraded to 6.x or newer, and or an AE Services upgrade or SA/UA recast (with existing CM 6+) or a license move is requested in a CM 6.x (or later) environment.

Account teams are responsible to initiate reconciliations and should perform an analysis of current license quantities. Once this analysis has been completed, Avaya Product Operations should be engaged to make the actual corrections within Avaya’s licensing tools. The following tasks should be performed by the account team with the customer:

  • Verify the license quantities in AES, CM, and PLDS.

  • Verify the license quantities purchased.

  • If the customer has licenses that were not purchased, determine the total license quantities along with the quantities that are in use.

    • Determine the quantities to be purchased and/or removed.

    • If licenses will be removed, determine what platform (CM, AES, PLDS) they will be removed from and the associated quantities.

The following additional information will assist in determining an accurate inventory count of the DMCC / CMAPI Basic licenses:

Note:

Some CM releases included a licensing quantity of 4-IP_API_As so the total license count may need to reflect this quantity.

Note:

Avaya Self-Service Offers add some additional complexity to determining the total license count because they use the IP_API_A with Voice Portal and Experience Portal H.323 connections and our Self-Service Offers support CM 6.x and 7.x (along with pre-PLDS CMs: CM 5.2.x with RFA). This needs to be taken into account in any reconciliation.