“Dadmin” in Avaya™ Communication Manager
Effective with the May 2002 release of Avaya Communication Manager 1.1, the activation of the BusinessPartner login, “dadmin” is controlled by the Remote Feature Activation (RFA) license. You will not need to call an Avaya Centralized Service Center. RFA Users can check “ON” this capability in the RFA license. Listed below are the rules and basic understanding surrounding activating “dadmin” in an RFA license:
1) This capability is identified in an RFA license as FEAT_DADMIN.
2) FEAT_DADMIN has a default setting of OFF in RFA and Avaya Communication Manager.
FEAT_DADMIN is capable of being turned ON/OFF on the features screen in RFA. Note that it is no longer possible to either activate or deactivate the dadmin login using the change login screen or change password screen. Deactivation of the dadmin login is controlled exclusively by the license file.
3) If FEAT_DADMIN is set to OFF in the switch, the dadmin login shall be disabled in DEFINITY, and on Linux platforms removed from the underlying operating system.
4) If FEAT_DADMIN is set to ON in the switch, the dadmin login shall be enabled.
5) When a license file is installed that changes FEAT_DADMIN from OFF to ON in the switch, the dadmin login shall be activated with a default password. The default dadmin password shall be the same across all platforms. That default password is “partner111”.
6) When a license file is installed that changes FEAT_DADMIN from ON to OFF in the switch, the dadmin login shall be disabled in Avaya Communication Manager , removed from the underlying operating system on Linux platforms, and any non-default dadmin password shall be reset back to void in Avaya Communication Manager.
7) DEFINITY shall require that the default dadmin password be changed upon first use of the dadmin login with the default password.
8) Upgrade Rules When Valid License Present:
When upgrading from an Avaya Communication Manager release prior to the availability of FEAT_DADMIN to an Avaya Communication Manager release that includes the FEAT_DADMIN feature, the following upgrade rules shall apply if a valid license file is present upon initialization after the upgrade:
· If the dadmin login was not enabled prior to the upgrade, and FEAT_DADMIN is OFF in the license file, then the dadmin login shall be disabled in the switch in accordance with requirement.
· If the dadmin login was not enabled prior to the upgrade, and FEAT_DADMIN is ON in the license file, then the dadmin login shall be enabled in the switch with the default password.
· If the dadmin login was enabled prior to the upgrade, and the FEAT_DADMIN is OFF in the license file, then the dadmin login shall be disabled in the switch in accordance with requirement.
· If the dadmin login was enabled prior to the upgrade, and the FEAT_DADMIN is ON in the license file, then the dadmin login shall be enabled in the switch and the dadmin password shall be unchanged (i.e. whatever password existed before the upgrade is still in place and is not reset to the default).
9) Upgrade Rules When Valid License Not Present
When upgrading from a DEFINITY release prior to the availability of FEAT_DADMIN to an Avaya Communication Manager release that includes the FEAT_DADMIN feature, the following upgrade rules shall apply if no valid license file is present upon initialization after the upgrade:
· If the upgrade is from R8 or later and the dadmin login was not enabled prior to the upgrade, then the dadmin login shall be disabled in the switch.
· If the upgrade is from R8 or later and the dadmin login was enabled prior to the upgrade, then the dadmin login shall be enabled in the switch and the dadmin password shall be unchanged (i.e. whatever password existed before the upgrade is still in place and is not reset to the default).
10) Error Messages when FEAT_DADMIN Is OFF
If a user attempts to execute the change login dadmin SAT command or change password dadmin SAT command when FEAT_DADMIN is OFF, Avaya Communication Manager shall return the following error message: Enable 'dadmin' login feature not assigned.
© 2003 Avaya Inc. All Rights Reserved. Avaya and the Avaya Logo are trademarks of Avaya Inc. or Avaya ECS Ltd., a wholly owned subsidiary of Avaya Inc. and may be registered in the US and other jurisdictions. All trademarks identified by ® and ™ are registered trademarks or trademarks, respectively, of Avaya Inc. All other registered trademarks or trademarks are property of their respective owners.
Revised 20-April-03
Avaya Inc. – Proprietary. Use pursuant to the terms of your signed agreement or company policy.
konri75