Dear Support,
We have a customer with AES 8.1.1 and we would like to register the stations (DMCC Multiple Registrations) without providing the station's password.
We understand what should be set up:
- The DeviceID contains the administered switch name associated with a valid switch connection to Communication Manager
- The switch connection to the Communication Manager is active and talking
- The SDB on the AE Server is enabled
- The user has "Unrestricted Access" in the SDB
- The extension’s class of restriction (COR) on the Communication Manager has:
- "Can Be Service Observed" set to "y"
- "Can Be a Service Observer" set to "y"
All above set up and they verified multiple times, also restarted services and AES, but we still receive this:
3000: Registration Reject reason: securityDenial Login Denied - Access Code invalid. diagnostic string= code= 63773

It used to work at other customers with older AES releases.

Do you have any idea what we should check?

Thanks and regards,
Gabor Fenyvesi

I see the following fixed MR in the Release Note for Avaya Aura® Application Enablement (AE) Services 8.1.1.0 Super Patch 2 (8.1.1.0.2). Maybe it is related to your problem:

AES-14892 Intermittent failure of DMCC registration with error: "Terminal Registered Response: reason: Registration Reject
reason: securityDenial Login Denied - Access Code invalid”

Apply SP2 and see if that fixes your problem.

Martin

They have upgraded to 8.1.1.0.2 and now the stations which were successfully registered previously can be registered without a password but the stations that were never registered still cannot be registered without a password.
Any hint?
Gabor

What do you mean by "the stations which were successfully registered previously can be registered without a password but the stations that were never registered still cannot be registered without a password"?

What is the difference between the stations that can register and the ones that can't?

Martin

Hi,
So they configure the correct password in our 3rd party application for a station and the application can register it, then they set an empty password in our 3rd party application and restart the application then it can register the extension successfully. If they never set the correct password in our 3rd party application for a station then the application cannot register it with an empty password.

I have got some additional information, they say that H.323 stations are always working properly:

We noticed that the passcode validation issue does not occur when an H.323 station is used. This applies to both the scenarios - new extensions and existing (already registered) extensions.
However, when an AST station is used, the passcode validation issue will occur for new extensions. The existing extensions will not be impacted by passcode change.
In AST, the user will login as SIP in ASM but getting feature from CM. So this extension type uses two protocols SIP and H.323. User will use the SIP station to make call and we believe the recorder will tap into the H.323 station in CM for recording.

Thanks,
Gabor Fenyvesi

Your customer should open a Service Request with their Business Partner or Avaya Client Services.

Martin

OK, thanks.
Gabor