ACR: DMCC ports not registering on ACR

Doc ID		SOLN270365
Version:		5.0
Status:		Published
Published date:		25 Jul 2023
Created Date:		17 Jun 2015

Author:

chengdongzhao

Details

Avaya ACR recorder incorrectly uses CM IP-API-A license.
ACR has 50 licenses, but when ACR startup, it finds the DMCC station is using CM IP-API-A licenses.

ACR Version 12

AES 6.3.3 Super Patch 1.

DMCC ports not registering on ACRv12, patch 1200141

Problem Clarification

ACR has 50 licenses, but when ACR startup, it find DMCC station is using CM IP-API-A license. Request to check the reason and fix the issue.

Gatekeeper/Gateway alarms in ACR

Cause

1. AES missed h.323 gate keeper configuration.
2. Communication Manager Name on ACR was configured with incorrect Switch Connection name or with an IP address.

Solution

1. Add H.323 gatekeeper with a CLAN IP.
2. From ACR Web page, configure Communication Manager Name which can find from AES Communication Manager connection setting.
After correct above setting, ACR DMCC stations correctly used AES Named license.

Avaya -- Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy