Avaya Agent for Desktop: Login Failure on Version 2.0.6.26.3008


Doc ID    SOLN386654
Version:    1.0
Status:    Published
Published date:    13 Jun 2026
Author:   
rappasahebbi
 

Details

  • Product: Avaya Agent for Desktop (AAFD) 2.0.6.26.3008 with Avaya Aura Communication Manager (version unchanged between tests).
  • Login failed only on AAFD 2.0.6.26.3008; the same station logged in successfully on AAFD 2.0.6.21.3003.
  • AAFD 2.0.6.26.3008 logs showed ICV (integrity check) authentication failures, “AuthenticateICV … failed,” and “incorrect password” with registration rejection.
  • Logs also showed first‑launch configuration copy failures (directive.txt, config.xml) and an empty AvayaAgentStation/station password entry in the new profile.
  • Issue could not be reproduced in Avaya lab; customer later confirmed successful login after installing an updated AAFD release that superseded 2.0.6.26.3008.

Problem Clarification

Login to Communication Manager failed only when using AAFD 2.0.6.26.3008, while earlier AAFD version 2.0.6.21.3003 worked with the same station.

Cause

The failure was due to incorrect or missing station password handling and first‑launch configuration copy issues in AAFD 2.0.6.26.3008, which caused ICV authentication and GCF validation to fail.
The behavior was specific to this build and was resolved by an updated AAFD release provided by the product team

Solution

  1. Collected AAFD client logs for both working (2.0.6.21.3003) and failing (2.0.6.26.3008) versions and compared registration flows with Communication Manager.
  2. Identified in the failing logs that:
    • ICV authentication failed with “AuthenticateICV … failed” and “incorrect password.”
    • Station password (AvayaAgentStation entry) was not stored in the new 2.0.6.26 profile.
    • First‑launch configuration files (directive.txt, config.xml) were not copied into the user profile, resulting in incomplete local configuration.
  3. Verified on Communication Manager that the H.323 security profile “challenge” setting and ip‑network‑region configuration were correct, confirming the issue was client‑side and specific to AAFD 2.0.6.26.3008.
  4. As an interim action, advised a clean reinstall of AAFD 2.0.6.26.3008 (uninstall, delete local AAFD profile/configuration, reinstall, and manually re‑enter station extension and password) to eliminate corrupted local profile data.
  5. Escalated the case to Avaya product engineering with logs, configuration details, and trace outputs; engineering confirmed GCF validation failure on port 3008 and non‑reproducibility in the lab.
  6. Product engineering prepared and provided an updated AAFD build (later than 2.0.6.26.3008, including a 3009 test build during analysis) that corrected the authentication/configuration handling defect.
  7. End user installed the updated AAFD release on the affected Windows 11 workstation and configured the station credentials again.
  8. End user confirmed successful login and stable operation with the updated AAFD release, and the SR was closed as resolved.

Notes: Confirm that all necessary permissions have been obtained and system backups are completed prior to implementing any changes. Service‑affecting actions such as client rollouts or changes to Communication Manager security profiles should be scheduled in accordance with maintenance windows and change‑management policies. If assistance is required with build selection or deployment, please open an online Service Request to engage Avaya for further assistance


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